Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368dad0ad9de7cb331f231346c0e5be3290422e9edd6171d8cbee5ac464cfa7e

Tx prefix hash: a252420f157b67663ef6b4838fb81cc78e88fcfb137d7beebc2ec62bf41a78e2
Tx public key: 579975e503598cedda942944c1472e3b53d4a47e2e2e51e6fe69a23ca374e45e
Timestamp: 1677195087 Timestamp [UCT]: 2023-02-23 23:31:27 Age [y:d:h:m:s]: 02:046:04:50:12
Block: 703571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554605 RingCT/type: yes/0
Extra: 01579975e503598cedda942944c1472e3b53d4a47e2e2e51e6fe69a23ca374e45e02110000000174b6d784000000000000000000

1 output(s) for total of 2.862708443000 dcy

stealth address amount amount idx
00: c73ff1d9d62fe308c106a00f049eb85bcedeea0c1c85fbef9c3047676dfea8ef 2.862708443000 1147174 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": 703581, "vin": [ { "gen": { "height": 703571 } } ], "vout": [ { "amount": 2862708443, "target": { "key": "c73ff1d9d62fe308c106a00f049eb85bcedeea0c1c85fbef9c3047676dfea8ef" } } ], "extra": [ 1, 87, 153, 117, 229, 3, 89, 140, 237, 218, 148, 41, 68, 193, 71, 46, 59, 83, 212, 164, 126, 46, 46, 81, 230, 254, 105, 162, 60, 163, 116, 228, 94, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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