Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25df978cfa4eb87ee7347c3809849e56ef1636fe35221ebd0d6e2520613b6a23

Tx prefix hash: d8c0bfea7840b354a09cbf688e597aca421c5b69df64c98dd55159305fd43e15
Tx public key: d09364caa87cfdcb3d618d05d21fd0fd4e42ebf264ae73b643f2868dbf42a575
Timestamp: 1763660762 Timestamp [UCT]: 2025-11-20 17:46:02 Age [y:d:h:m:s]: 00:005:21:15:47
Block: 1416391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4218 RingCT/type: yes/0
Extra: 01d09364caa87cfdcb3d618d05d21fd0fd4e42ebf264ae73b643f2868dbf42a57502110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f62cc20b835414e12e9145ebddcd8e7fee956c4d3ea7faa678979bc7b4394f40 0.600000000000 1904910 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": 1416401, "vin": [ { "gen": { "height": 1416391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f62cc20b835414e12e9145ebddcd8e7fee956c4d3ea7faa678979bc7b4394f40" } } ], "extra": [ 1, 208, 147, 100, 202, 168, 124, 253, 203, 61, 97, 141, 5, 210, 31, 208, 253, 78, 66, 235, 242, 100, 174, 115, 182, 67, 242, 134, 141, 191, 66, 165, 117, 2, 17, 0, 0, 0, 6, 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