Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1233404c897a04fcd663845761791347d9f911ac86516840964e9c23a9efe33b

Tx prefix hash: 487a9cb920163a294ff1afc85099c29bf8b7423a8bc3d425902cb66c759b704e
Tx public key: 6df9bc476490efb3c77e2cf68d2a6342a67bdc4fb4f41beb262b693b5e139203
Timestamp: 1763846815 Timestamp [UCT]: 2025-11-22 21:26:55 Age [y:d:h:m:s]: 00:004:12:50:32
Block: 1417926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3262 RingCT/type: yes/0
Extra: 016df9bc476490efb3c77e2cf68d2a6342a67bdc4fb4f41beb262b693b5e13920302110000000c70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57c1061f5c6bf8cfdb1120cb048abb3c365943de80a810a4aad01af653610a5 0.600000000000 1906453 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": 1417936, "vin": [ { "gen": { "height": 1417926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57c1061f5c6bf8cfdb1120cb048abb3c365943de80a810a4aad01af653610a5" } } ], "extra": [ 1, 109, 249, 188, 71, 100, 144, 239, 179, 199, 126, 44, 246, 141, 42, 99, 66, 166, 123, 220, 79, 180, 244, 27, 235, 38, 43, 105, 59, 94, 19, 146, 3, 2, 17, 0, 0, 0, 12, 112, 96, 157, 3, 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