Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4083bfbc459174b367cdfd1bf3e7b0cac13655726da5760bed90bec9ea9bcc0c

Tx prefix hash: 0fd2de9cdf58d9e79f8d1fd8abb84eb29f882c31de89e19fd2bba28c5419708c
Tx public key: 820feda5a427bf7b93291bdc3858d589564e5fb49d90a8bad6e1c3db8ce26ea1
Timestamp: 1745083193 Timestamp [UCT]: 2025-04-19 17:19:53 Age [y:d:h:m:s]: 00:215:22:34:37
Block: 1265019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152023 RingCT/type: yes/0
Extra: 01820feda5a427bf7b93291bdc3858d589564e5fb49d90a8bad6e1c3db8ce26ea102110000000cdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21768d0f6a6ecf25cc110adf5a189db4f89fac5a45ff5e05b88616aef684e95 0.600000000000 1752222 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": 1265029, "vin": [ { "gen": { "height": 1265019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21768d0f6a6ecf25cc110adf5a189db4f89fac5a45ff5e05b88616aef684e95" } } ], "extra": [ 1, 130, 15, 237, 165, 164, 39, 191, 123, 147, 41, 27, 220, 56, 88, 213, 137, 86, 78, 95, 180, 157, 144, 168, 186, 214, 225, 195, 219, 140, 226, 110, 161, 2, 17, 0, 0, 0, 12, 219, 181, 113, 193, 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