Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e77e5e2f54cba0aa04103033fd21a09cdfb5a163aca0bba278aea1ca2050a45

Tx prefix hash: b61b6501d6e52e53e11fe1bf414706ea1266b534000253de80d0d5c98e938459
Tx public key: 954dbcedde98aa756cf5c22f4ddac8e4477f6a0398fbefaf58ad11a5e0b1543f
Timestamp: 1721330531 Timestamp [UCT]: 2024-07-18 19:22:11 Age [y:d:h:m:s]: 00:259:13:08:03
Block: 1068602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185403 RingCT/type: yes/0
Extra: 01954dbcedde98aa756cf5c22f4ddac8e4477f6a0398fbefaf58ad11a5e0b1543f02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a517f26695d73b3887c59e5c837daea21a41880fd183052082e294b3f04e4814 0.600000000000 1539695 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": 1068612, "vin": [ { "gen": { "height": 1068602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a517f26695d73b3887c59e5c837daea21a41880fd183052082e294b3f04e4814" } } ], "extra": [ 1, 149, 77, 188, 237, 222, 152, 170, 117, 108, 245, 194, 47, 77, 218, 200, 228, 71, 127, 106, 3, 152, 251, 239, 175, 88, 173, 17, 165, 224, 177, 84, 63, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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