Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96a382e33dd001bc7e217e75367c49e7919923e43cf353ac5122722c6e81c1b

Tx prefix hash: e3cc6303bc0706c251967423fde1348ed231d8cf8b8d338cde2f4e87aaf6a087
Tx public key: 4c08c353f07046b4cdd449b0976b8b95c2d6a5c5ddd783ca936f08530e9ffaa8
Timestamp: 1694569176 Timestamp [UCT]: 2023-09-13 01:39:36 Age [y:d:h:m:s]: 01:148:09:08:57
Block: 846901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367131 RingCT/type: yes/0
Extra: 014c08c353f07046b4cdd449b0976b8b95c2d6a5c5ddd783ca936f08530e9ffaa80211000000064b8f5122000000000000000000

1 output(s) for total of 0.959103515000 dcy

stealth address amount amount idx
00: b4c635d121d97822fc3c4002af374567a384dde984f8da93082321fbc7cd80c4 0.959103515000 1300393 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": 846911, "vin": [ { "gen": { "height": 846901 } } ], "vout": [ { "amount": 959103515, "target": { "key": "b4c635d121d97822fc3c4002af374567a384dde984f8da93082321fbc7cd80c4" } } ], "extra": [ 1, 76, 8, 195, 83, 240, 112, 70, 180, 205, 212, 73, 176, 151, 107, 139, 149, 194, 214, 165, 197, 221, 215, 131, 202, 147, 111, 8, 83, 14, 159, 250, 168, 2, 17, 0, 0, 0, 6, 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