Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dd40c02ae0f225f2de544c0a3f685b6f50d220d13eb281ee9c0f0cce7c77d8d

Tx prefix hash: 06096439ddeb9a64b8c67cb60bcbd0bf2d8f790ccf596b5eade0db9dd93749c8
Tx public key: 3638024dfbf33f4b8c526babe7b4e74cf07ef5d56b3098fa3916637ee77dbf88
Timestamp: 1751180786 Timestamp [UCT]: 2025-06-29 07:06:26 Age [y:d:h:m:s]: 00:190:14:30:40
Block: 1315052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134413 RingCT/type: yes/0
Extra: 013638024dfbf33f4b8c526babe7b4e74cf07ef5d56b3098fa3916637ee77dbf8802110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e69b554cadd6014d2272c71c66e83fdfca1d0ea39e43efcb69be1a5e960c93 0.600000000000 1802705 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": 1315062, "vin": [ { "gen": { "height": 1315052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e69b554cadd6014d2272c71c66e83fdfca1d0ea39e43efcb69be1a5e960c93" } } ], "extra": [ 1, 54, 56, 2, 77, 251, 243, 63, 75, 140, 82, 107, 171, 231, 180, 231, 76, 240, 126, 245, 213, 107, 48, 152, 250, 57, 22, 99, 126, 231, 125, 191, 136, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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