Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa2ee5ce7a2fdc5291bf29849aacbf2428308289c91db06b795155ee4a8b30d

Tx prefix hash: 64666631c14e1b4deb64423646ecf93ad401bd94db20b607b18e3db66bd65ab7
Tx public key: 320a43f4a5ccc931a9b0ceaf91cc4ef01207d621697f920f5e0d142a3a6ca49a
Timestamp: 1752576608 Timestamp [UCT]: 2025-07-15 10:50:08 Age [y:d:h:m:s]: 00:172:08:50:06
Block: 1325963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122006 RingCT/type: yes/0
Extra: 01320a43f4a5ccc931a9b0ceaf91cc4ef01207d621697f920f5e0d142a3a6ca49a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a743cef422b804c61b41c563af70c354bb860d0ce9a2d47c6cd35f99aa0616ad 0.600000000000 1813712 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": 1325973, "vin": [ { "gen": { "height": 1325963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a743cef422b804c61b41c563af70c354bb860d0ce9a2d47c6cd35f99aa0616ad" } } ], "extra": [ 1, 50, 10, 67, 244, 165, 204, 201, 49, 169, 176, 206, 175, 145, 204, 78, 240, 18, 7, 214, 33, 105, 127, 146, 15, 94, 13, 20, 42, 58, 108, 164, 154, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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