Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e1ad54a2e31b452934a69581ea134b9143b22d6539a0b09778107691541a44

Tx prefix hash: 23aa5d6362734e9a3cfb726804094fe496ec199121cb49755eb6a87c62835c12
Tx public key: 13848a4ad6ed8e6b7662f830477f534eaea0b193a31e4df0653cae9792c1d6eb
Timestamp: 1749760297 Timestamp [UCT]: 2025-06-12 20:31:37 Age [y:d:h:m:s]: 00:150:01:32:50
Block: 1303685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104972 RingCT/type: yes/0
Extra: 0113848a4ad6ed8e6b7662f830477f534eaea0b193a31e4df0653cae9792c1d6eb02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa6411d39e095dd8b1100724a7851dc67a0cf53f09317266a8ee9e635826ba7e 0.600000000000 1791268 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": 1303695, "vin": [ { "gen": { "height": 1303685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa6411d39e095dd8b1100724a7851dc67a0cf53f09317266a8ee9e635826ba7e" } } ], "extra": [ 1, 19, 132, 138, 74, 214, 237, 142, 107, 118, 98, 248, 48, 71, 127, 83, 78, 174, 160, 177, 147, 163, 30, 77, 240, 101, 60, 174, 151, 146, 193, 214, 235, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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