Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec20722acc2827c2aceda3d9a9d11f61343628081deeb877af09f72dcd97817

Tx prefix hash: 2726230aa0a011fb9b5a1f253c2bf7c40e6a088b86afef3d5dd5e98678edf3d3
Tx public key: 9ebe0a1aa7a6e5d502561666c4e118ddb1b559e61ff96463852b0238fa3fc72f
Timestamp: 1762005691 Timestamp [UCT]: 2025-11-01 14:01:31 Age [y:d:h:m:s]: 00:004:11:48:32
Block: 1402711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3170 RingCT/type: yes/0
Extra: 019ebe0a1aa7a6e5d502561666c4e118ddb1b559e61ff96463852b0238fa3fc72f02110000000ddf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250a37e9b1b8d4a88900d7c2c37806afdca4799e2632495adc077d0e7a6c747a 0.600000000000 1891030 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": 1402721, "vin": [ { "gen": { "height": 1402711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250a37e9b1b8d4a88900d7c2c37806afdca4799e2632495adc077d0e7a6c747a" } } ], "extra": [ 1, 158, 190, 10, 26, 167, 166, 229, 213, 2, 86, 22, 102, 196, 225, 24, 221, 177, 181, 89, 230, 31, 249, 100, 99, 133, 43, 2, 56, 250, 63, 199, 47, 2, 17, 0, 0, 0, 13, 223, 90, 36, 122, 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