Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a8abaa7aa7bc745041224ae03d535ab48dd1303be597262ef00be541cebae1

Tx prefix hash: a307d25a17427e768791abb562d08c8ae0bdfa9b4d811c49d5de54ba4d8e9d34
Tx public key: e1c467cdd2e8ecb9d97d91e847138713e70dd060434889ae409c91d54e6cdf44
Timestamp: 1713781823 Timestamp [UCT]: 2024-04-22 10:30:23 Age [y:d:h:m:s]: 01:015:22:44:48
Block: 1006005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272344 RingCT/type: yes/0
Extra: 01e1c467cdd2e8ecb9d97d91e847138713e70dd060434889ae409c91d54e6cdf4402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13b099e9b308fb05512e73f674ce5d4f26d74381a59eac5373632c145ae02a9f 0.600000000000 1466889 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": 1006015, "vin": [ { "gen": { "height": 1006005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13b099e9b308fb05512e73f674ce5d4f26d74381a59eac5373632c145ae02a9f" } } ], "extra": [ 1, 225, 196, 103, 205, 210, 232, 236, 185, 217, 125, 145, 232, 71, 19, 135, 19, 231, 13, 208, 96, 67, 72, 137, 174, 64, 156, 145, 213, 78, 108, 223, 68, 2, 17, 0, 0, 0, 6, 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