Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0731b727aafbfeb8a330b69ba0efb282453aa24dfee3aeb2c5e6ca081f593d0

Tx prefix hash: 7f4439b246cec0ee6d430aa13e87a506a065e027670f77621f13f3f4c125cc88
Tx public key: 718c1c75495079ced1a668072fe8280af73ee06ea23dccabaf1b24734f378ce3
Timestamp: 1698574309 Timestamp [UCT]: 2023-10-29 10:11:49 Age [y:d:h:m:s]: 01:169:03:06:36
Block: 880143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381864 RingCT/type: yes/0
Extra: 01718c1c75495079ced1a668072fe8280af73ee06ea23dccabaf1b24734f378ce30211000000014b8f5122000000000000000000

1 output(s) for total of 0.744253505000 dcy

stealth address amount amount idx
00: a574bda2cdab999c9ae7a94db74d0942cc894b9796edda5571d02e5222a398d0 0.744253505000 1335689 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": 880153, "vin": [ { "gen": { "height": 880143 } } ], "vout": [ { "amount": 744253505, "target": { "key": "a574bda2cdab999c9ae7a94db74d0942cc894b9796edda5571d02e5222a398d0" } } ], "extra": [ 1, 113, 140, 28, 117, 73, 80, 121, 206, 209, 166, 104, 7, 47, 232, 40, 10, 247, 62, 224, 110, 162, 61, 204, 171, 175, 27, 36, 115, 79, 55, 140, 227, 2, 17, 0, 0, 0, 1, 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