Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107ef929e9dff89746b91c6f48ea3a501e627209461680787bfbfb194ed960f3

Tx prefix hash: 9f10c1c9698ba1c20ec3a9791c901406adf03b723d60d95a1f9c261132ac75e5
Tx public key: 9f9aec8b38ba327363c265bdefcbe24b31def2b68ca2522e30773850a1c877d6
Timestamp: 1744050215 Timestamp [UCT]: 2025-04-07 18:23:35 Age [y:d:h:m:s]: 00:224:23:06:42
Block: 1256435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158526 RingCT/type: yes/0
Extra: 019f9aec8b38ba327363c265bdefcbe24b31def2b68ca2522e30773850a1c877d6021100000010dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db3240b40df035d479187c5b4e84fe8296f1d156de5f6ed193d9a2a26c2181fc 0.600000000000 1743548 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": 1256445, "vin": [ { "gen": { "height": 1256435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db3240b40df035d479187c5b4e84fe8296f1d156de5f6ed193d9a2a26c2181fc" } } ], "extra": [ 1, 159, 154, 236, 139, 56, 186, 50, 115, 99, 194, 101, 189, 239, 203, 226, 75, 49, 222, 242, 182, 140, 162, 82, 46, 48, 119, 56, 80, 161, 200, 119, 214, 2, 17, 0, 0, 0, 16, 219, 181, 113, 193, 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