Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 687d4e5b5d7aa546fd88ce1556b6f8d7287d94a8c8bcf1cb5435493beac1d9ac

Tx prefix hash: c29e0403a2809f8f53434b815dd3f4829581ce0d514d498bd11c71b93e96ded2
Tx public key: 2304b11dd4e475048331a79e1dc0c79e492ff6ee1f456e0a8aca7c114e3fbbac
Timestamp: 1706483947 Timestamp [UCT]: 2024-01-28 23:19:07 Age [y:d:h:m:s]: 01:069:01:49:10
Block: 945477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310443 RingCT/type: yes/0
Extra: 012304b11dd4e475048331a79e1dc0c79e492ff6ee1f456e0a8aca7c114e3fbbac0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37e867ba98c2f27a6530bb7a27ae4a9e1219fd1c99207001d158456e6034c5c0 0.600000000000 1403791 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": 945487, "vin": [ { "gen": { "height": 945477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37e867ba98c2f27a6530bb7a27ae4a9e1219fd1c99207001d158456e6034c5c0" } } ], "extra": [ 1, 35, 4, 177, 29, 212, 228, 117, 4, 131, 49, 167, 158, 29, 192, 199, 158, 73, 47, 246, 238, 31, 69, 110, 10, 138, 202, 124, 17, 78, 63, 187, 172, 2, 17, 0, 0, 0, 6, 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