Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da69ba7970dd35b50920f910cee5caa5fe20f80f58203aa99c97a74f6ebc2bc

Tx prefix hash: 53c1f5f35237481720295f71d3557f5052dcf9e7ee6953252d692180f549bd55
Tx public key: 1c0e0c84389abbb1a16c3f6feb1590ff3ff08a485ad40d7147e9b596d294dba1
Timestamp: 1635140181 Timestamp [UCT]: 2021-10-25 05:36:21 Age [y:d:h:m:s]: 03:011:20:09:42
Block: 359970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 786792 RingCT/type: yes/0
Extra: 011c0e0c84389abbb1a16c3f6feb1590ff3ff08a485ad40d7147e9b596d294dba10211000000057e786c8c000000000000000000

1 output(s) for total of 39.379515479000 dcy

stealth address amount amount idx
00: 90887cec8027b70033fa7f5c1e0377f8296321584444f30a98d402cd01a87580 39.379515479000 732805 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": 359980, "vin": [ { "gen": { "height": 359970 } } ], "vout": [ { "amount": 39379515479, "target": { "key": "90887cec8027b70033fa7f5c1e0377f8296321584444f30a98d402cd01a87580" } } ], "extra": [ 1, 28, 14, 12, 132, 56, 154, 187, 177, 161, 108, 63, 111, 235, 21, 144, 255, 63, 240, 138, 72, 90, 212, 13, 113, 71, 233, 181, 150, 210, 148, 219, 161, 2, 17, 0, 0, 0, 5, 126, 120, 108, 140, 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