Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a36dcdaf30b82b00a78792530c3b3845a18bd563ab9c35a19d49a494c25d110

Tx prefix hash: f000e9782e7713022c2a7525cb02faf3117e8c58b5c6af2b7712815cbb92157e
Tx public key: 3cef00ce7e8092caa8013a5f8b719f67d768afd2de46fa2ae19f2846b151e024
Timestamp: 1761029198 Timestamp [UCT]: 2025-10-21 06:46:38 Age [y:d:h:m:s]: 00:092:17:25:50
Block: 1394599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66241 RingCT/type: yes/0
Extra: 013cef00ce7e8092caa8013a5f8b719f67d768afd2de46fa2ae19f2846b151e02402110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d39bc85f91d336156747b128f2b9d1a5dd390197b9e879e918f0c6ecefffd1e 0.600000000000 1882872 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": 1394609, "vin": [ { "gen": { "height": 1394599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d39bc85f91d336156747b128f2b9d1a5dd390197b9e879e918f0c6ecefffd1e" } } ], "extra": [ 1, 60, 239, 0, 206, 126, 128, 146, 202, 168, 1, 58, 95, 139, 113, 159, 103, 215, 104, 175, 210, 222, 70, 250, 42, 225, 159, 40, 70, 177, 81, 224, 36, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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