Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a45a157667a8edf1f5fe5f575ecc0070fd215522333d2f8d60e088477688e8

Tx prefix hash: 353c071a1d4eb42c514e6428f53b9fb130333c4d0d9bf2287832e13c36969fc2
Tx public key: ca2d87d0e1ff54ca84fb0e40d658b23a25dd55fd48de857badb3e6354e7a735c
Timestamp: 1752661849 Timestamp [UCT]: 2025-07-16 10:30:49 Age [y:d:h:m:s]: 00:124:13:17:54
Block: 1326656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87772 RingCT/type: yes/0
Extra: 01ca2d87d0e1ff54ca84fb0e40d658b23a25dd55fd48de857badb3e6354e7a735c02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b1e7e4c9d0997c461e9490893aac9884f4102e9e292784abb333595d7439bb5 0.600000000000 1814407 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": 1326666, "vin": [ { "gen": { "height": 1326656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b1e7e4c9d0997c461e9490893aac9884f4102e9e292784abb333595d7439bb5" } } ], "extra": [ 1, 202, 45, 135, 208, 225, 255, 84, 202, 132, 251, 14, 64, 214, 88, 178, 58, 37, 221, 85, 253, 72, 222, 133, 123, 173, 179, 230, 53, 78, 122, 115, 92, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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