Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efbc550b28548e987367e3f0cbc938528b418f1326784feba5d99c0406e7a26

Tx prefix hash: c74b16b3d93f7564955408ffeb4a28e8f2c86fc68fc4b54fcefd7b944a1fd1c3
Tx public key: 129c449d2a94f213183c51e92528c9064d5374f046557e9f879084c2a790de6f
Timestamp: 1658621605 Timestamp [UCT]: 2022-07-24 00:13:25 Age [y:d:h:m:s]: 02:165:00:47:28
Block: 550310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639372 RingCT/type: yes/0
Extra: 01129c449d2a94f213183c51e92528c9064d5374f046557e9f879084c2a790de6f02110000000275e3f0e9000000000000000000

1 output(s) for total of 9.217107596000 dcy

stealth address amount amount idx
00: 05f032867794c9e98f66156dc99d741326e31d1620989f5a72e48c6599951058 9.217107596000 981775 of 0

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": 550320, "vin": [ { "gen": { "height": 550310 } } ], "vout": [ { "amount": 9217107596, "target": { "key": "05f032867794c9e98f66156dc99d741326e31d1620989f5a72e48c6599951058" } } ], "extra": [ 1, 18, 156, 68, 157, 42, 148, 242, 19, 24, 60, 81, 233, 37, 40, 201, 6, 77, 83, 116, 240, 70, 85, 126, 159, 135, 144, 132, 194, 167, 144, 222, 111, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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