Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 204e9cf28a97ef01db638529cf2dbbd69d3267f7dd1cfc7feedf07ad652cef28

Tx prefix hash: 89e153556b8e26c95c4254ba99e78d31626a88fc6750c3f2b2afa0a09d93a5b6
Tx public key: 62fb3851653bba5d668946cd814f6b70a9c1234f89da81fd56b47b827e0d9a7f
Timestamp: 1758212579 Timestamp [UCT]: 2025-09-18 16:22:59 Age [y:d:h:m:s]: 00:094:18:22:25
Block: 1371245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67852 RingCT/type: yes/0
Extra: 0162fb3851653bba5d668946cd814f6b70a9c1234f89da81fd56b47b827e0d9a7f021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 206eeaefd6e1b8277aed9bb0ba30ae06a088562cc0d87b240f8e805d247f5a6e 0.600000000000 1859322 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": 1371255, "vin": [ { "gen": { "height": 1371245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "206eeaefd6e1b8277aed9bb0ba30ae06a088562cc0d87b240f8e805d247f5a6e" } } ], "extra": [ 1, 98, 251, 56, 81, 101, 59, 186, 93, 102, 137, 70, 205, 129, 79, 107, 112, 169, 193, 35, 79, 137, 218, 129, 253, 86, 180, 123, 130, 126, 13, 154, 127, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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