Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6463d8b254ec467ff6de75579e4352fd1b37f74fffd7d75ca6b9217e22c8f59

Tx prefix hash: b9ea994e077137c1bf1398b8f4826082e13a81bc206061fcc3fe53879f114f64
Tx public key: 5e3472f2ae3630ea22766ba33d3f105ace9e8c31b18b612f12a31f10213d4929
Timestamp: 1711799900 Timestamp [UCT]: 2024-03-30 11:58:20 Age [y:d:h:m:s]: 01:055:04:25:48
Block: 989595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300424 RingCT/type: yes/0
Extra: 015e3472f2ae3630ea22766ba33d3f105ace9e8c31b18b612f12a31f10213d492902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86116cedc95fd906a3b65b39cd04072939a8dfc5c2b6ff7a3d46438c0bdb95ef 0.600000000000 1449894 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": 989605, "vin": [ { "gen": { "height": 989595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86116cedc95fd906a3b65b39cd04072939a8dfc5c2b6ff7a3d46438c0bdb95ef" } } ], "extra": [ 1, 94, 52, 114, 242, 174, 54, 48, 234, 34, 118, 107, 163, 61, 63, 16, 90, 206, 158, 140, 49, 177, 139, 97, 47, 18, 163, 31, 16, 33, 61, 73, 41, 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