Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e7574e9ac03636e8acbb753bf1f2fcbf49029074cabc783a27fd862d5f8aaa

Tx prefix hash: a091f4cbce88f597c816d98dbd96d40f9ddf248e9ccb9021b137e5f1ce327922
Tx public key: 444aa4ddd054874ea83e9192b774f824fad86259b38b83848fea7c1f24dd03d8
Timestamp: 1727932782 Timestamp [UCT]: 2024-10-03 05:19:42 Age [y:d:h:m:s]: 00:112:15:52:21
Block: 1123322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80500 RingCT/type: yes/0
Extra: 01444aa4ddd054874ea83e9192b774f824fad86259b38b83848fea7c1f24dd03d802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd04276c11be8edc668f71f7e472b7461f9b6d9feda3a26a7cd02355d6c3730e 0.600000000000 1605855 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": 1123332, "vin": [ { "gen": { "height": 1123322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd04276c11be8edc668f71f7e472b7461f9b6d9feda3a26a7cd02355d6c3730e" } } ], "extra": [ 1, 68, 74, 164, 221, 208, 84, 135, 78, 168, 62, 145, 146, 183, 116, 248, 36, 250, 216, 98, 89, 179, 139, 131, 132, 143, 234, 124, 31, 36, 221, 3, 216, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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