Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f742df70b5884029ee7d37741d284701b8145fca4d5a9992bf5bb3fc5236f0cd

Tx prefix hash: 3ea50972b3cf14f00fd68b45d6e281d2ba0a11deb9c05f831ee8e22d92953d6d
Tx public key: a817e8148d702d92ce59f1bc17b60e7692679471dcd75e8308bcec7ba13c3ac1
Timestamp: 1735151626 Timestamp [UCT]: 2024-12-25 18:33:46 Age [y:d:h:m:s]: 00:127:09:34:49
Block: 1183053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90852 RingCT/type: yes/0
Extra: 01a817e8148d702d92ce59f1bc17b60e7692679471dcd75e8308bcec7ba13c3ac102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c680ff5d8deaf87a22ae4d6a3ad9894da3bc44ff994d3e08b01d5837ab20c5e3 0.600000000000 1669492 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": 1183063, "vin": [ { "gen": { "height": 1183053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c680ff5d8deaf87a22ae4d6a3ad9894da3bc44ff994d3e08b01d5837ab20c5e3" } } ], "extra": [ 1, 168, 23, 232, 20, 141, 112, 45, 146, 206, 89, 241, 188, 23, 182, 14, 118, 146, 103, 148, 113, 220, 215, 94, 131, 8, 188, 236, 123, 161, 60, 58, 193, 2, 17, 0, 0, 0, 10, 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