Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a1e9a191c62dc368f113a029370665bb86bb88cb4e704d9ad91541866d73284

Tx prefix hash: b2655b72a05fb53d980d08a79b42c21f7a64b2386527b9e414fb7e7d9f48510c
Tx public key: ddf220d5410e9d06ef94ae896b94b595a07ff4450391fce1601ad4c35c753d0c
Timestamp: 1634844191 Timestamp [UCT]: 2021-10-21 19:23:11 Age [y:d:h:m:s]: 03:238:13:36:12
Block: 357638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 948483 RingCT/type: yes/0
Extra: 01ddf220d5410e9d06ef94ae896b94b595a07ff4450391fce1601ad4c35c753d0c0211000000108d0de867000000000000000000

1 output(s) for total of 40.088218466000 dcy

stealth address amount amount idx
00: 1f94847dfde2a16b1b8c53a9d343128bf26f53d23f372fca4c21c3d5932fd9f9 40.088218466000 729174 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": 357648, "vin": [ { "gen": { "height": 357638 } } ], "vout": [ { "amount": 40088218466, "target": { "key": "1f94847dfde2a16b1b8c53a9d343128bf26f53d23f372fca4c21c3d5932fd9f9" } } ], "extra": [ 1, 221, 242, 32, 213, 65, 14, 157, 6, 239, 148, 174, 137, 107, 148, 181, 149, 160, 127, 244, 69, 3, 145, 252, 225, 96, 26, 212, 195, 92, 117, 61, 12, 2, 17, 0, 0, 0, 16, 141, 13, 232, 103, 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