Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2a03816dc8cb776be9719236fab6d3dad9fb992fb4394a6b1d721a2e0d7654

Tx prefix hash: 8b6cf7c692703426de2e5b5c5238f8840a48ee0472d419d517919c28151f13d6
Tx public key: d9227eee7a6811c2308c12e91054bf64986e5535525b9769f4fd5c284b5dcbde
Timestamp: 1705058540 Timestamp [UCT]: 2024-01-12 11:22:20 Age [y:d:h:m:s]: 01:044:15:50:10
Block: 933668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292984 RingCT/type: yes/0
Extra: 01d9227eee7a6811c2308c12e91054bf64986e5535525b9769f4fd5c284b5dcbde02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4829353eae7f1d35c18f6de542e0a5c4ed0eecb7403e6fccce2ef3f272982a85 0.600000000000 1391638 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": 933678, "vin": [ { "gen": { "height": 933668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4829353eae7f1d35c18f6de542e0a5c4ed0eecb7403e6fccce2ef3f272982a85" } } ], "extra": [ 1, 217, 34, 126, 238, 122, 104, 17, 194, 48, 140, 18, 233, 16, 84, 191, 100, 152, 110, 85, 53, 82, 91, 151, 105, 244, 253, 92, 40, 75, 93, 203, 222, 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