Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1028404924af15c98aa2fa5fd4b73f88fdf025e09c24b9efaed1e27e082977f1

Tx prefix hash: c8e9226a811f2b65b52b7254f2b08031a3c46a4b1e9aae862ce82afa1d517dc8
Tx public key: 1392ebb07c22a408a1c8db26fbe9900a153e443c879f599ea857c773a9adc151
Timestamp: 1714029760 Timestamp [UCT]: 2024-04-25 07:22:40 Age [y:d:h:m:s]: 01:029:12:58:38
Block: 1008051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282073 RingCT/type: yes/0
Extra: 011392ebb07c22a408a1c8db26fbe9900a153e443c879f599ea857c773a9adc15102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d18675a7f08188e9b0fdcd4119c9a498e47bef6f0eaf3868f44ae5f85e24df84 0.600000000000 1469517 of 15

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": 1008061, "vin": [ { "gen": { "height": 1008051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d18675a7f08188e9b0fdcd4119c9a498e47bef6f0eaf3868f44ae5f85e24df84" } } ], "extra": [ 1, 19, 146, 235, 176, 124, 34, 164, 8, 161, 200, 219, 38, 251, 233, 144, 10, 21, 62, 68, 60, 135, 159, 89, 158, 168, 87, 199, 115, 169, 173, 193, 81, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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