Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5222fab1aa0b58c765174aa8a8a7ee0051edf656a8c321e17defa01223405c8d

Tx prefix hash: 45978e0678353103faaaa6753733b70b6ce2ab3b5433cdb6bb39f49c1e9e5375
Tx public key: 3bf8a960eebeaf97f7e2834b72b61d079feba116c448123501d3924bcb81e2d5
Timestamp: 1579214761 Timestamp [UCT]: 2020-01-16 22:46:01 Age [y:d:h:m:s]: 04:318:13:00:16
Block: 47118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117130 RingCT/type: yes/0
Extra: 013bf8a960eebeaf97f7e2834b72b61d079feba116c448123501d3924bcb81e2d50211000000098a2ee0d9000000000000000000

1 output(s) for total of 428.443926880000 dcy

stealth address amount amount idx
00: 46f64a951cc58551804288617b2aea07f4ec915c7a72e0db40dce347b048e42d 428.443926880000 87039 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": 47128, "vin": [ { "gen": { "height": 47118 } } ], "vout": [ { "amount": 428443926880, "target": { "key": "46f64a951cc58551804288617b2aea07f4ec915c7a72e0db40dce347b048e42d" } } ], "extra": [ 1, 59, 248, 169, 96, 238, 190, 175, 151, 247, 226, 131, 75, 114, 182, 29, 7, 159, 235, 161, 22, 196, 72, 18, 53, 1, 211, 146, 75, 203, 129, 226, 213, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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