Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4c688a3480026ddd00f8c999c14cb591d1f231b9f180df6648e95f0fc3c91961

Tx prefix hash: 371cd9dbb82489b900f91c59823f3726a17a4ab254c301e1a322ed3cda76da2d
Tx public key: 49c70c21316c5ac55955ead598d7cefaf8a0286ab1efd9e15045b0610b86097b
Timestamp: 1734252217 Timestamp [UCT]: 2024-12-15 08:43:37 Age [y:d:h:m:s]: 00:094:22:08:27
Block: 1175616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67629 RingCT/type: yes/0
Extra: 0149c70c21316c5ac55955ead598d7cefaf8a0286ab1efd9e15045b0610b86097b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c84914c1a34415f56efa077cf4353069a94c18b8b6f96bb2e6af0e57a23a37ac 0.600000000000 1661921 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1175626, "vin": [ { "gen": { "height": 1175616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c84914c1a34415f56efa077cf4353069a94c18b8b6f96bb2e6af0e57a23a37ac" } } ], "extra": [ 1, 73, 199, 12, 33, 49, 108, 90, 197, 89, 85, 234, 213, 152, 215, 206, 250, 248, 160, 40, 106, 177, 239, 217, 225, 80, 69, 176, 97, 11, 134, 9, 123, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8