Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d88ac259740e51f220ca56b33affa73429a108d67c95d852d40debae26bbece

Tx prefix hash: 8d329545c7574411fd13688c24336241e3812dfb0c8f72063bd558526b8320ca
Tx public key: 1fb8bb128405d9ea1c77ed96b6a8800e5d12510d21065bc59c3449ae0afb062a
Timestamp: 1754608735 Timestamp [UCT]: 2025-08-07 23:18:55 Age [y:d:h:m:s]: 00:103:14:49:38
Block: 1342437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73133 RingCT/type: yes/0
Extra: 011fb8bb128405d9ea1c77ed96b6a8800e5d12510d21065bc59c3449ae0afb062a021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c563cce51f22de906bae9eec7a2781a6b3f2c51f7ea7b19689146a0231ae6c5 0.600000000000 1830268 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": 1342447, "vin": [ { "gen": { "height": 1342437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c563cce51f22de906bae9eec7a2781a6b3f2c51f7ea7b19689146a0231ae6c5" } } ], "extra": [ 1, 31, 184, 187, 18, 132, 5, 217, 234, 28, 119, 237, 150, 182, 168, 128, 14, 93, 18, 81, 13, 33, 6, 91, 197, 156, 52, 73, 174, 10, 251, 6, 42, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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