Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7083a501757860e25a3cc4f4e7ef15ce443ad3e699fe68ce7122fe1eba5718fe

Tx prefix hash: c71b1afdcf0c1f1401dbc695bb447866184bd8b575aed17e51e6d3180cfd6e7a
Tx public key: 7ac1a21f1d5f2eb9b5c2653ba914e368e9e842c0a3048971b0a9c574117cb866
Timestamp: 1750863833 Timestamp [UCT]: 2025-06-25 15:03:53 Age [y:d:h:m:s]: 00:141:17:46:37
Block: 1312585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99255 RingCT/type: yes/0
Extra: 017ac1a21f1d5f2eb9b5c2653ba914e368e9e842c0a3048971b0a9c574117cb866021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1895421186fb1d53e57df11ff76355c78428dc14392e4eeec6d90107d3aaae2 0.600000000000 1800218 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": 1312595, "vin": [ { "gen": { "height": 1312585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1895421186fb1d53e57df11ff76355c78428dc14392e4eeec6d90107d3aaae2" } } ], "extra": [ 1, 122, 193, 162, 31, 29, 95, 46, 185, 181, 194, 101, 59, 169, 20, 227, 104, 233, 232, 66, 192, 163, 4, 137, 113, 176, 169, 197, 116, 17, 124, 184, 102, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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