Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf567977ee8664a514b65dcfdb62514eecbb4a0e946c1818405791b6ec94b272

Tx prefix hash: ac5ffcad67f3ee3d613d9163c352efc44985b1c8aa9a2643e2b1e8e00445e7c3
Tx public key: be9783a5a6010e4f8e7375e8318661cf8f6837017a9ae3bf04c35800cf277cec
Timestamp: 1750891824 Timestamp [UCT]: 2025-06-25 22:50:24 Age [y:d:h:m:s]: 00:138:09:20:27
Block: 1312791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96874 RingCT/type: yes/0
Extra: 01be9783a5a6010e4f8e7375e8318661cf8f6837017a9ae3bf04c35800cf277cec021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84ad26514d8f86b9e144bc7308cec2c388af3294bc2b442f0aa6489ea9b34535 0.600000000000 1800426 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": 1312801, "vin": [ { "gen": { "height": 1312791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84ad26514d8f86b9e144bc7308cec2c388af3294bc2b442f0aa6489ea9b34535" } } ], "extra": [ 1, 190, 151, 131, 165, 166, 1, 14, 79, 142, 115, 117, 232, 49, 134, 97, 207, 143, 104, 55, 1, 122, 154, 227, 191, 4, 195, 88, 0, 207, 39, 124, 236, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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