Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de76441c7b260f59e9f740d1377055a3c7e114ff86bc8b8c543039bfa98374f

Tx prefix hash: 32401f45213f88de6c1098ffb21e89460f10adcc7b09656593c6cbaf635de954
Tx public key: 1eef2bbe49e059a253d132698443b73540d9fe4b5d2ebfea5a4d67ff76a8cf80
Timestamp: 1714600382 Timestamp [UCT]: 2024-05-01 21:53:02 Age [y:d:h:m:s]: 00:348:05:15:17
Block: 1012796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248911 RingCT/type: yes/0
Extra: 011eef2bbe49e059a253d132698443b73540d9fe4b5d2ebfea5a4d67ff76a8cf8002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575c6f2cac4874ed55ad90a483b036a2adb621e56b1f611ac60a475c4e0ad4d9 0.600000000000 1475424 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": 1012806, "vin": [ { "gen": { "height": 1012796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575c6f2cac4874ed55ad90a483b036a2adb621e56b1f611ac60a475c4e0ad4d9" } } ], "extra": [ 1, 30, 239, 43, 190, 73, 224, 89, 162, 83, 209, 50, 105, 132, 67, 183, 53, 64, 217, 254, 75, 93, 46, 191, 234, 90, 77, 103, 255, 118, 168, 207, 128, 2, 17, 0, 0, 0, 1, 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