Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 610fd0fad9ce0b255bef7ad36c8a2ed53bc91cfd900ae2d42eaf77e325fdae9b

Tx prefix hash: bb40ef1973f2d2569eb19262469328ed2c068de4b185363ca1aab2f8adc7be19
Tx public key: 84d1fb56b2774531b30bec70e6efb76bd6807cd2c0cc3a63dd3d10cda78db8f6
Timestamp: 1751256552 Timestamp [UCT]: 2025-06-30 04:09:12 Age [y:d:h:m:s]: 00:178:19:01:41
Block: 1315591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126025 RingCT/type: yes/0
Extra: 0184d1fb56b2774531b30bec70e6efb76bd6807cd2c0cc3a63dd3d10cda78db8f6021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05767d8f455e2168eab4fb78b860235f8aff9955e1ea6af78608c1ce5122d3b6 0.600000000000 1803246 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": 1315601, "vin": [ { "gen": { "height": 1315591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05767d8f455e2168eab4fb78b860235f8aff9955e1ea6af78608c1ce5122d3b6" } } ], "extra": [ 1, 132, 209, 251, 86, 178, 119, 69, 49, 179, 11, 236, 112, 230, 239, 183, 107, 214, 128, 124, 210, 192, 204, 58, 99, 221, 61, 16, 205, 167, 141, 184, 246, 2, 17, 0, 0, 0, 3, 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