Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4db49e73b4fcd8d3262e5c4b27197048553f93c594a54e4f49580847b36c4a

Tx prefix hash: bf102f7769a14686ff70f4c7146e4d9dc283bc4345ff812a52fb7a869484ce70
Tx public key: 58dab033465296358c16e1257f77592df68ca012badf6f7e5515ef2cca510c14
Timestamp: 1633724642 Timestamp [UCT]: 2021-10-08 20:24:02 Age [y:d:h:m:s]: 03:030:18:07:16
Block: 349347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 799234 RingCT/type: yes/0
Extra: 0158dab033465296358c16e1257f77592df68ca012badf6f7e5515ef2cca510c1402110000000237cb3088000000000000000000

1 output(s) for total of 42.704023168000 dcy

stealth address amount amount idx
00: 262c5b39a410f2195b5bd3be7b662a766ae50e503c6bef4ebd4a0f1bbce84043 42.704023168000 715270 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": 349357, "vin": [ { "gen": { "height": 349347 } } ], "vout": [ { "amount": 42704023168, "target": { "key": "262c5b39a410f2195b5bd3be7b662a766ae50e503c6bef4ebd4a0f1bbce84043" } } ], "extra": [ 1, 88, 218, 176, 51, 70, 82, 150, 53, 140, 22, 225, 37, 127, 119, 89, 45, 246, 140, 160, 18, 186, 223, 111, 126, 85, 21, 239, 44, 202, 81, 12, 20, 2, 17, 0, 0, 0, 2, 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