Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 885d557dd802f3907a97a0a3e368a904b81426e7d231e9b1bd5a53aae810ee81

Tx prefix hash: 3e642082bf6dee0ab2bf9be665c49e5615f4e36470bc8d72e54191bf4a53b055
Tx public key: b4cb66d2f52875b0e5211b39e44e022fb4979f3aff39502af71b2aac9fb6093c
Timestamp: 1626886010 Timestamp [UCT]: 2021-07-21 16:46:50 Age [y:d:h:m:s]: 03:296:03:35:59
Block: 298359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 983178 RingCT/type: yes/0
Extra: 01b4cb66d2f52875b0e5211b39e44e022fb4979f3aff39502af71b2aac9fb6093c02110000002637cb3088000000000000000000

1 output(s) for total of 63.010550106000 dcy

stealth address amount amount idx
00: 1df0ce404de808771bcdb2d0053ce03b3c55db80eda5f1c90966578aeb5d769d 63.010550106000 624202 of 0

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": 298369, "vin": [ { "gen": { "height": 298359 } } ], "vout": [ { "amount": 63010550106, "target": { "key": "1df0ce404de808771bcdb2d0053ce03b3c55db80eda5f1c90966578aeb5d769d" } } ], "extra": [ 1, 180, 203, 102, 210, 245, 40, 117, 176, 229, 33, 27, 57, 228, 78, 2, 47, 180, 151, 159, 58, 255, 57, 80, 42, 247, 27, 42, 172, 159, 182, 9, 60, 2, 17, 0, 0, 0, 38, 55, 203, 48, 136, 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