Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 525a0933d7c7d6549f59dd0786d5369b60552acd1e5de626062984e595466fcc

Tx prefix hash: 6280a05bc2d6fbb7bd9fb7a46f539a16906e700b0bf131100bf6b51f7e3ac233
Tx public key: f1f9fbcae4bf80c4d3a928d79d32aafd21838fc0ad9654dd21da22edf7ea0cfe
Timestamp: 1749565615 Timestamp [UCT]: 2025-06-10 14:26:55 Age [y:d:h:m:s]: 00:151:09:03:12
Block: 1302114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105858 RingCT/type: yes/0
Extra: 01f1f9fbcae4bf80c4d3a928d79d32aafd21838fc0ad9654dd21da22edf7ea0cfe0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca7a34e85d826bfa8d517c87984d773258624e38cc219702814f64f4a261d5b4 0.600000000000 1789683 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": 1302124, "vin": [ { "gen": { "height": 1302114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca7a34e85d826bfa8d517c87984d773258624e38cc219702814f64f4a261d5b4" } } ], "extra": [ 1, 241, 249, 251, 202, 228, 191, 128, 196, 211, 169, 40, 215, 157, 50, 170, 253, 33, 131, 143, 192, 173, 150, 84, 221, 33, 218, 34, 237, 247, 234, 12, 254, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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