Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0704426c5f869eeb061f04b69caffe9c41741770ad52474d1837a6bda2cf226a

Tx prefix hash: 6fbb664f4a5b1515be4d92fe1a6567d9a361c36603dcb75494c90e0eb56176d2
Tx public key: a1a9bb33c29709d4d0ec5819d2c5a6ab1a86d374822f2436bb7f3fea5553164e
Timestamp: 1715109829 Timestamp [UCT]: 2024-05-07 19:23:49 Age [y:d:h:m:s]: 01:041:13:51:34
Block: 1017017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290540 RingCT/type: yes/0
Extra: 01a1a9bb33c29709d4d0ec5819d2c5a6ab1a86d374822f2436bb7f3fea5553164e0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 653517877682852c926f8d40fb5453ffa93fc5c22d81c5b530adb2a86065141f 0.600000000000 1480772 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": 1017027, "vin": [ { "gen": { "height": 1017017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "653517877682852c926f8d40fb5453ffa93fc5c22d81c5b530adb2a86065141f" } } ], "extra": [ 1, 161, 169, 187, 51, 194, 151, 9, 212, 208, 236, 88, 25, 210, 197, 166, 171, 26, 134, 211, 116, 130, 47, 36, 54, 187, 127, 63, 234, 85, 83, 22, 78, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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