Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6a32829dfee6b3d5483e28ef85822e31988db9bd2c8fab2c75caff86abc0ad

Tx prefix hash: 664f62896fd433fdd5cf9283dd59732555d93c113aae0311834d534428866be0
Tx public key: f8c7e09ca8021e0501fdbfd3ecbac2a2c4ed835c6786cd550635eaa9f4fce07c
Timestamp: 1710621446 Timestamp [UCT]: 2024-03-16 20:37:26 Age [y:d:h:m:s]: 01:018:14:19:16
Block: 979821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274256 RingCT/type: yes/0
Extra: 01f8c7e09ca8021e0501fdbfd3ecbac2a2c4ed835c6786cd550635eaa9f4fce07c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a63ae489d30f05340ab3cb7be590abdcffca26d37bd5b6e455744077f7d31356 0.600000000000 1439876 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": 979831, "vin": [ { "gen": { "height": 979821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a63ae489d30f05340ab3cb7be590abdcffca26d37bd5b6e455744077f7d31356" } } ], "extra": [ 1, 248, 199, 224, 156, 168, 2, 30, 5, 1, 253, 191, 211, 236, 186, 194, 162, 196, 237, 131, 92, 103, 134, 205, 85, 6, 53, 234, 169, 244, 252, 224, 124, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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