Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b9f0d6efffbc53f3b4d4d54b7f4df9d1c33ae5239ac7c8dd11cbe2fe8b6b215

Tx prefix hash: 656462a3ca9d10407487bdedcad09ab4cd6c1441531712d3f3f3b9afdb21fb68
Tx public key: 42318462952a1986e7ab99e816dd79670c1020a146ae3df65cc2f5f0237cc53a
Timestamp: 1765566752 Timestamp [UCT]: 2025-12-12 19:12:32 Age [y:d:h:m:s]: 00:020:04:02:08
Block: 1432195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14442 RingCT/type: yes/0
Extra: 0142318462952a1986e7ab99e816dd79670c1020a146ae3df65cc2f5f0237cc53a021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a63243178042106cb9e546fdf4b50943abfc8764b91cd69f1c96da665b3cd15 0.600000000000 1920974 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": 1432205, "vin": [ { "gen": { "height": 1432195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a63243178042106cb9e546fdf4b50943abfc8764b91cd69f1c96da665b3cd15" } } ], "extra": [ 1, 66, 49, 132, 98, 149, 42, 25, 134, 231, 171, 153, 232, 22, 221, 121, 103, 12, 16, 32, 161, 70, 174, 61, 246, 92, 194, 245, 240, 35, 124, 197, 58, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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