Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f6b04c662862eb6614d20b71e287327672a453a7f5825d2694a27e7e68d778e

Tx prefix hash: e257afdfab4b9100ce2382702d62bd7d7050875a6ed64ccc3c0f346997ffd9e3
Tx public key: e6f97ecffefff1993e45f4bd051fd5fb721ec32b754fb4aa72d69c34c39e9465
Timestamp: 1704600558 Timestamp [UCT]: 2024-01-07 04:09:18 Age [y:d:h:m:s]: 01:159:01:02:27
Block: 929865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374752 RingCT/type: yes/0
Extra: 01e6f97ecffefff1993e45f4bd051fd5fb721ec32b754fb4aa72d69c34c39e946502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b9947ac10227bc80cfefdab3686dc2a4966cc6e9ebac58ac0e751c335bcaa86 0.600000000000 1387741 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": 929875, "vin": [ { "gen": { "height": 929865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b9947ac10227bc80cfefdab3686dc2a4966cc6e9ebac58ac0e751c335bcaa86" } } ], "extra": [ 1, 230, 249, 126, 207, 254, 255, 241, 153, 62, 69, 244, 189, 5, 31, 213, 251, 114, 30, 195, 43, 117, 79, 180, 170, 114, 214, 156, 52, 195, 158, 148, 101, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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