Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977d57330843ba300a063bfbfd6163e76c697a78b4b1a9d63e7e234c00c7981b

Tx prefix hash: ebc6d62c0323f21280344572e1c4174e81a453f7775a907a6d04368712d43b2c
Tx public key: 9e791e6ab503ae76922294441d4be232b0a1cd9602cfa0a4ed2d5a6189024f38
Timestamp: 1748601813 Timestamp [UCT]: 2025-05-30 10:43:33 Age [y:d:h:m:s]: 00:168:07:42:46
Block: 1294145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117978 RingCT/type: yes/0
Extra: 019e791e6ab503ae76922294441d4be232b0a1cd9602cfa0a4ed2d5a6189024f3802110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e196848b878f771e78f5497edb59ce2c32c6c0aa6fffa1205f8ce3aeacffe080 0.600000000000 1781640 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": 1294155, "vin": [ { "gen": { "height": 1294145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e196848b878f771e78f5497edb59ce2c32c6c0aa6fffa1205f8ce3aeacffe080" } } ], "extra": [ 1, 158, 121, 30, 106, 181, 3, 174, 118, 146, 34, 148, 68, 29, 75, 226, 50, 176, 161, 205, 150, 2, 207, 160, 164, 237, 45, 90, 97, 137, 2, 79, 56, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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