Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c670b2799708bcc96ebe83d98944a404cf9ae1431a7bc8c4cba6c95c797b1362

Tx prefix hash: bd92bacb968e6a4a6e540845f451bbff86f348ce425b1ae53bac849fe9ec0d55
Tx public key: e151f74f0a17e5b4cc30da7fe335a87ad2be900ebffeb221dc5ee3ae6c1ab62e
Timestamp: 1716046408 Timestamp [UCT]: 2024-05-18 15:33:28 Age [y:d:h:m:s]: 00:236:04:26:08
Block: 1024775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169041 RingCT/type: yes/0
Extra: 01e151f74f0a17e5b4cc30da7fe335a87ad2be900ebffeb221dc5ee3ae6c1ab62e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85ae7a78165714a62420b8d34cbef6806d0985e98552d7ea79340936bed5a70d 0.600000000000 1490788 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": 1024785, "vin": [ { "gen": { "height": 1024775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85ae7a78165714a62420b8d34cbef6806d0985e98552d7ea79340936bed5a70d" } } ], "extra": [ 1, 225, 81, 247, 79, 10, 23, 229, 180, 204, 48, 218, 127, 227, 53, 168, 122, 210, 190, 144, 14, 191, 254, 178, 33, 220, 94, 227, 174, 108, 26, 182, 46, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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