Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5b2ed81828916038db85b40b5d1accb08e873e4e29b6138c2ecd226f231ac8

Tx prefix hash: 0b147aa9b278a590b00f64bf5f0e9717835db68e5e63bacb06067a1d6750f058
Tx public key: e726a269a86d5740e0e68df7a1a332a79af37503f39536819cb2f6bba27a865e
Timestamp: 1715090082 Timestamp [UCT]: 2024-05-07 13:54:42 Age [y:d:h:m:s]: 00:189:21:38:56
Block: 1016859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135929 RingCT/type: yes/0
Extra: 01e726a269a86d5740e0e68df7a1a332a79af37503f39536819cb2f6bba27a865e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f30a1e492898787befe303ca596c3e4f0631f38b130abdb1b14869926eb9d3 0.600000000000 1480568 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": 1016869, "vin": [ { "gen": { "height": 1016859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f30a1e492898787befe303ca596c3e4f0631f38b130abdb1b14869926eb9d3" } } ], "extra": [ 1, 231, 38, 162, 105, 168, 109, 87, 64, 224, 230, 141, 247, 161, 163, 50, 167, 154, 243, 117, 3, 243, 149, 54, 129, 156, 178, 246, 187, 162, 122, 134, 94, 2, 17, 0, 0, 0, 4, 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