Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39595d3fdcd18bcbf4432fcf183a89ed011d072ae1f037c135efed9767b1cde1

Tx prefix hash: f6870fae8de101f17c4eaaa9fbacd076e84dcb7f92f5f0072d381bb9fc1a7ee1
Tx public key: 2b53a7a245c73a77bc0e59c44238f5b715455709675d6e3319fc1594236d99be
Timestamp: 1731917387 Timestamp [UCT]: 2024-11-18 08:09:47 Age [y:d:h:m:s]: 00:140:00:40:47
Block: 1156265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99887 RingCT/type: yes/0
Extra: 012b53a7a245c73a77bc0e59c44238f5b715455709675d6e3319fc1594236d99be021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f71d264f21d420306bb9a1665fc012ab4051fe9429a035d5e43b5fb9a78c36d 0.600000000000 1641888 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": 1156275, "vin": [ { "gen": { "height": 1156265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f71d264f21d420306bb9a1665fc012ab4051fe9429a035d5e43b5fb9a78c36d" } } ], "extra": [ 1, 43, 83, 167, 162, 69, 199, 58, 119, 188, 14, 89, 196, 66, 56, 245, 183, 21, 69, 87, 9, 103, 93, 110, 51, 25, 252, 21, 148, 35, 109, 153, 190, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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