Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3209d7daed8b606dd3c642bc84e7fafb0f7f911532a8994407e8f5eb690159c2

Tx prefix hash: 3788be2487446ac0613e5efb9ab7a70f67fdc763c0e56eaca0850dc813cdd08a
Tx public key: 42e3642067a4640ec2ca1158a87ec1b74a854c57bc76d656eb7f046307255ca3
Timestamp: 1657932309 Timestamp [UCT]: 2022-07-16 00:45:09 Age [y:d:h:m:s]: 02:140:19:37:41
Block: 544639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622016 RingCT/type: yes/0
Extra: 0142e3642067a4640ec2ca1158a87ec1b74a854c57bc76d656eb7f046307255ca3021100000001e6d27f9c000000000000000000

1 output(s) for total of 9.624652158000 dcy

stealth address amount amount idx
00: d72f7f0cdb919a2c5be0fb5553c82d8adcfdcfaa1ee27b322b9ef5e3bec1bbf2 9.624652158000 975440 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": 544649, "vin": [ { "gen": { "height": 544639 } } ], "vout": [ { "amount": 9624652158, "target": { "key": "d72f7f0cdb919a2c5be0fb5553c82d8adcfdcfaa1ee27b322b9ef5e3bec1bbf2" } } ], "extra": [ 1, 66, 227, 100, 32, 103, 164, 100, 14, 194, 202, 17, 88, 168, 126, 193, 183, 74, 133, 76, 87, 188, 118, 214, 86, 235, 127, 4, 99, 7, 37, 92, 163, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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