Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b1704a9199b333bb50b6d1bab654ac54711cd6ec9304fa5a69cf489c61d5ed

Tx prefix hash: 680a8757f25c6e508bcfcd21b1ead5a1b5529afff3d6075af4736e3b835abe5e
Tx public key: 4820241468587914e2d7adc56d67842940014c9a5d0e820d12844a2f0b795d84
Timestamp: 1656818108 Timestamp [UCT]: 2022-07-03 03:15:08 Age [y:d:h:m:s]: 02:257:10:15:48
Block: 535484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705109 RingCT/type: yes/0
Extra: 014820241468587914e2d7adc56d67842940014c9a5d0e820d12844a2f0b795d8402110000000ba8c141c5000000000000000000

1 output(s) for total of 10.320942810000 dcy

stealth address amount amount idx
00: 4f0ba9c3d44a2a0035d773d2b2a998412037f8e5a558dab155f33d785e16f603 10.320942810000 965119 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": 535494, "vin": [ { "gen": { "height": 535484 } } ], "vout": [ { "amount": 10320942810, "target": { "key": "4f0ba9c3d44a2a0035d773d2b2a998412037f8e5a558dab155f33d785e16f603" } } ], "extra": [ 1, 72, 32, 36, 20, 104, 88, 121, 20, 226, 215, 173, 197, 109, 103, 132, 41, 64, 1, 76, 154, 93, 14, 130, 13, 18, 132, 74, 47, 11, 121, 93, 132, 2, 17, 0, 0, 0, 11, 168, 193, 65, 197, 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