Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83943c5b357ddc17dc2e76f59a553b495673d608a0cbc4121e7d1fdf6014cd73

Tx prefix hash: a82287b9f413fdc47549a12edbb6ace3b2ffc34e3ab31419e36ea6fe607edf4f
Tx public key: 2ffd7f16dc0024f7987f8b5c845fdb7f20ccf23d3cf4baabf2ca43bc5429f2ee
Timestamp: 1697216249 Timestamp [UCT]: 2023-10-13 16:57:29 Age [y:d:h:m:s]: 02:022:12:47:15
Block: 868869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535712 RingCT/type: yes/0
Extra: 012ffd7f16dc0024f7987f8b5c845fdb7f20ccf23d3cf4baabf2ca43bc5429f2ee021100000007faf35c9c000000000000000000

1 output(s) for total of 0.811103634000 dcy

stealth address amount amount idx
00: aee6af4cda687426a589a4e06ca2587ccdf8653f45ec867f64e3af74c75e1256 0.811103634000 1323690 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": 868879, "vin": [ { "gen": { "height": 868869 } } ], "vout": [ { "amount": 811103634, "target": { "key": "aee6af4cda687426a589a4e06ca2587ccdf8653f45ec867f64e3af74c75e1256" } } ], "extra": [ 1, 47, 253, 127, 22, 220, 0, 36, 247, 152, 127, 139, 92, 132, 95, 219, 127, 32, 204, 242, 61, 60, 244, 186, 171, 242, 202, 67, 188, 84, 41, 242, 238, 2, 17, 0, 0, 0, 7, 250, 243, 92, 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