Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f3dac61cf7cb39e316f68a311514b293bb3aeb93135b5292d370fde7575adf8

Tx prefix hash: 562a6c3b5bc236f9bd033bca57e9cc57858e20b3fc5f17effef5dcdbd5de8b40
Tx public key: 86f747974cfa983cbb195e450a39e2baa6e9757302171d3d5a910dc4f5df012c
Timestamp: 1708510978 Timestamp [UCT]: 2024-02-21 10:22:58 Age [y:d:h:m:s]: 01:289:00:47:13
Block: 962307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465340 RingCT/type: yes/0
Extra: 0186f747974cfa983cbb195e450a39e2baa6e9757302171d3d5a910dc4f5df012c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fd5fd1e3206e14d9baf8a6132f013164cbe0b36470aa7114eb6556dd2bce4d5 0.600000000000 1421940 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": 962317, "vin": [ { "gen": { "height": 962307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fd5fd1e3206e14d9baf8a6132f013164cbe0b36470aa7114eb6556dd2bce4d5" } } ], "extra": [ 1, 134, 247, 71, 151, 76, 250, 152, 60, 187, 25, 94, 69, 10, 57, 226, 186, 166, 233, 117, 115, 2, 23, 29, 61, 90, 145, 13, 196, 245, 223, 1, 44, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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