Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de3957b19be4ffb27a90d2dd5ec17a0ef67467bcd9f6ccc781f7f10486d66c2

Tx prefix hash: 38ac43bf78a9742794e8a3457edf6675911c81a9c9f239c0269e87977130ddd9
Tx public key: 6987d3268ba96f0b9301b463a5b0e4a0c5ceb98bfbe85acdc386b4dbdf33b2a4
Timestamp: 1645488162 Timestamp [UCT]: 2022-02-22 00:02:42 Age [y:d:h:m:s]: 02:305:00:16:09
Block: 443678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737426 RingCT/type: yes/0
Extra: 016987d3268ba96f0b9301b463a5b0e4a0c5ceb98bfbe85acdc386b4dbdf33b2a40211000000014a0f5013000000000000000000

1 output(s) for total of 20.792700334000 dcy

stealth address amount amount idx
00: a0372f184c0df303d859e067f2294343c27d4f2151ae935b49e1d38119d3b6c7 20.792700334000 856775 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": 443688, "vin": [ { "gen": { "height": 443678 } } ], "vout": [ { "amount": 20792700334, "target": { "key": "a0372f184c0df303d859e067f2294343c27d4f2151ae935b49e1d38119d3b6c7" } } ], "extra": [ 1, 105, 135, 211, 38, 139, 169, 111, 11, 147, 1, 180, 99, 165, 176, 228, 160, 197, 206, 185, 139, 251, 232, 90, 205, 195, 134, 180, 219, 223, 51, 178, 164, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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