Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77046c062a3b38452b559a851a416ddee08e6cb8867cb69a51e185a11a38104a

Tx prefix hash: 91d19b837c46af1ef6c80096f75bc9f051dbb2d64d2eacb666e716444485719b
Tx public key: 067a24f8051724e977abfd0bb1cd9cc6d036f0ec8dde315d99dd82f6feae7b3c
Timestamp: 1724766740 Timestamp [UCT]: 2024-08-27 13:52:20 Age [y:d:h:m:s]: 00:208:15:43:18
Block: 1097067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148976 RingCT/type: yes/0
Extra: 01067a24f8051724e977abfd0bb1cd9cc6d036f0ec8dde315d99dd82f6feae7b3c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d07ea0b375ee18c437e18ee05ba2b6a5302d4dd051860edd9094fddeb93915ba 0.600000000000 1572354 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": 1097077, "vin": [ { "gen": { "height": 1097067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d07ea0b375ee18c437e18ee05ba2b6a5302d4dd051860edd9094fddeb93915ba" } } ], "extra": [ 1, 6, 122, 36, 248, 5, 23, 36, 233, 119, 171, 253, 11, 177, 205, 156, 198, 208, 54, 240, 236, 141, 222, 49, 93, 153, 221, 130, 246, 254, 174, 123, 60, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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