Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79327579626d5a1c04daf129e95c3bb005388cb90b537fe4dd5791a7b2faf0d7

Tx prefix hash: 8a02200d2a77bae5b6ae60d047b703a29af830a4afaa4280875231e7e700a606
Tx public key: b4aa0f21fb695cc095dfd86e471b797836c1e456eab66e526be0920122173859
Timestamp: 1659517533 Timestamp [UCT]: 2022-08-03 09:05:33 Age [y:d:h:m:s]: 02:238:13:57:06
Block: 557709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 691720 RingCT/type: yes/0
Extra: 01b4aa0f21fb695cc095dfd86e471b797836c1e456eab66e526be092012217385902110000000165468698000000000000000000

1 output(s) for total of 8.711214104000 dcy

stealth address amount amount idx
00: e81e2c62084dbf63932e261de619cfb52a411a25ba61c6d90a066e44e72583f3 8.711214104000 989735 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": 557719, "vin": [ { "gen": { "height": 557709 } } ], "vout": [ { "amount": 8711214104, "target": { "key": "e81e2c62084dbf63932e261de619cfb52a411a25ba61c6d90a066e44e72583f3" } } ], "extra": [ 1, 180, 170, 15, 33, 251, 105, 92, 192, 149, 223, 216, 110, 71, 27, 121, 120, 54, 193, 228, 86, 234, 182, 110, 82, 107, 224, 146, 1, 34, 23, 56, 89, 2, 17, 0, 0, 0, 1, 101, 70, 134, 152, 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