Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b38ed07d2b82bcc66fdb62bffe57ebc68ac85455a174c2f7a52e1843b20c79d6

Tx prefix hash: f63dab404be9e972bcf847f11b6b59c1a5a93b0d2d6cf5e3c9fa2ba9103614b8
Tx public key: 75e552b0d64dc81da5d4e8b11ed93f574ae02116b6c39dd2f3e5a7ef83ba6cde
Timestamp: 1695323878 Timestamp [UCT]: 2023-09-21 19:17:58 Age [y:d:h:m:s]: 01:198:12:27:39
Block: 853173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402950 RingCT/type: yes/0
Extra: 0175e552b0d64dc81da5d4e8b11ed93f574ae02116b6c39dd2f3e5a7ef83ba6cde0211000000074b8f5122000000000000000000

1 output(s) for total of 0.914289504000 dcy

stealth address amount amount idx
00: 9434fe7d85f0dcbb3c60bfea1cbb6039690de3082441ff5306be433aa520132c 0.914289504000 1307057 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": 853183, "vin": [ { "gen": { "height": 853173 } } ], "vout": [ { "amount": 914289504, "target": { "key": "9434fe7d85f0dcbb3c60bfea1cbb6039690de3082441ff5306be433aa520132c" } } ], "extra": [ 1, 117, 229, 82, 176, 214, 77, 200, 29, 165, 212, 232, 177, 30, 217, 63, 87, 74, 224, 33, 22, 182, 195, 157, 210, 243, 229, 167, 239, 131, 186, 108, 222, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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