Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f7e90f220036723c12c58d46ff8800c597ae3cf7ef91e9f33ffae30abd8930

Tx prefix hash: 0da6c318ea44e09e4ea864b750f0b79d4b0e8494663b791edef0b34414007c4d
Tx public key: ecc1134c45e7a34a9a46399272277e33c1786689dcf60c597974fc62ee783c33
Timestamp: 1699422325 Timestamp [UCT]: 2023-11-08 05:45:25 Age [y:d:h:m:s]: 01:193:22:22:10
Block: 886957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399827 RingCT/type: yes/0
Extra: 01ecc1134c45e7a34a9a46399272277e33c1786689dcf60c597974fc62ee783c3302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.706550598000 dcy

stealth address amount amount idx
00: df5a283dc70b4940cfc908aecd8f15de0fb78454eed05042dc3095d9a5160623 0.706550598000 1342804 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": 886967, "vin": [ { "gen": { "height": 886957 } } ], "vout": [ { "amount": 706550598, "target": { "key": "df5a283dc70b4940cfc908aecd8f15de0fb78454eed05042dc3095d9a5160623" } } ], "extra": [ 1, 236, 193, 19, 76, 69, 231, 163, 74, 154, 70, 57, 146, 114, 39, 126, 51, 193, 120, 102, 137, 220, 246, 12, 89, 121, 116, 252, 98, 238, 120, 60, 51, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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