Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9b7aff3a9ceee7c9ea33afed64b7fd65300f6f28a0529cd6f0ff2ce5fd4491

Tx prefix hash: 49f2728b172acb49e25af08d3c03e6db990b57a2f99b75dfa49ac6d1c8e2e5dc
Tx public key: 01354f57d6939cf303b30894d4ad9921fcf317b7e8d74c5fb56fd773a27bde61
Timestamp: 1762562941 Timestamp [UCT]: 2025-11-08 00:49:01 Age [y:d:h:m:s]: 00:055:12:04:07
Block: 1407304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39746 RingCT/type: yes/0
Extra: 0101354f57d6939cf303b30894d4ad9921fcf317b7e8d74c5fb56fd773a27bde610211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ab9e513f4d51f923a56f92b6b5db3c8682ab1cad557d023f449fd2f272526cd 0.600000000000 1895723 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": 1407314, "vin": [ { "gen": { "height": 1407304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ab9e513f4d51f923a56f92b6b5db3c8682ab1cad557d023f449fd2f272526cd" } } ], "extra": [ 1, 1, 53, 79, 87, 214, 147, 156, 243, 3, 179, 8, 148, 212, 173, 153, 33, 252, 243, 23, 183, 232, 215, 76, 95, 181, 111, 215, 115, 162, 123, 222, 97, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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