Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d14e85dda393d77d61f17bf3c19a99bbcd1e525a390f89808191fe5c7f5d0686

Tx prefix hash: 18cccd61e820b4422f05ac95d735ab3ab329ae38a4b80b11f1aa31cb8ba9346e
Tx public key: ee35b2bd9294eada6b8907b7145dc56d97a50a1237610ae9b80845adcaba8f7d
Timestamp: 1704944604 Timestamp [UCT]: 2024-01-11 03:43:24 Age [y:d:h:m:s]: 01:082:19:20:35
Block: 932718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320281 RingCT/type: yes/0
Extra: 01ee35b2bd9294eada6b8907b7145dc56d97a50a1237610ae9b80845adcaba8f7d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c70fe8bf315f295b9c5033a10a62c18622b0158cd038d84bf9271ace9e9a8592 0.600000000000 1390658 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": 932728, "vin": [ { "gen": { "height": 932718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c70fe8bf315f295b9c5033a10a62c18622b0158cd038d84bf9271ace9e9a8592" } } ], "extra": [ 1, 238, 53, 178, 189, 146, 148, 234, 218, 107, 137, 7, 183, 20, 93, 197, 109, 151, 165, 10, 18, 55, 97, 10, 233, 184, 8, 69, 173, 202, 186, 143, 125, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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