Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c683b387c0bdaf92b669c40cb0120a53df8fb88ad4dc31015eb78ff7a6d6b15

Tx prefix hash: 84324460fefebc0fed49e9a28a8e1787307c485ac0cc6e4b2c06c128bda32390
Tx public key: cec9b5d96ac0809ec633288d928a2eda249f914d4a386afa99c4d451b6ff38bc
Timestamp: 1685452781 Timestamp [UCT]: 2023-05-30 13:19:41 Age [y:d:h:m:s]: 01:312:21:59:06
Block: 771395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484834 RingCT/type: yes/0
Extra: 01cec9b5d96ac0809ec633288d928a2eda249f914d4a386afa99c4d451b6ff38bc02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.706272202000 dcy

stealth address amount amount idx
00: b4ef7fa0056c319f67551c383fdf49e39607232b91ab84a4a1934d1fb3674f1b 1.706272202000 1220760 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": 771405, "vin": [ { "gen": { "height": 771395 } } ], "vout": [ { "amount": 1706272202, "target": { "key": "b4ef7fa0056c319f67551c383fdf49e39607232b91ab84a4a1934d1fb3674f1b" } } ], "extra": [ 1, 206, 201, 181, 217, 106, 192, 128, 158, 198, 51, 40, 141, 146, 138, 46, 218, 36, 159, 145, 77, 74, 56, 106, 250, 153, 196, 212, 81, 182, 255, 56, 188, 2, 17, 0, 0, 0, 1, 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