Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 887b35ef2c5866aef94235a0a1cb3d9698fd5a8dc3754af145c059597fe4fd73

Tx prefix hash: 700436e7801df105c7a499709a941723e8f103f6ab3c87dfde2907bbb3798d08
Tx public key: f1b86ae99023d5b4af9a80f027c9bcf3b1a1ae607d3a900007530d4e2307a23a
Timestamp: 1756013274 Timestamp [UCT]: 2025-08-24 05:27:54 Age [y:d:h:m:s]: 00:094:08:50:36
Block: 1353197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67391 RingCT/type: yes/0
Extra: 01f1b86ae99023d5b4af9a80f027c9bcf3b1a1ae607d3a900007530d4e2307a23a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e28df60003d8f813c39dec814f252a1bb148b777b0d62aea2faf8688feebb1b2 0.600000000000 1841170 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": 1353207, "vin": [ { "gen": { "height": 1353197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e28df60003d8f813c39dec814f252a1bb148b777b0d62aea2faf8688feebb1b2" } } ], "extra": [ 1, 241, 184, 106, 233, 144, 35, 213, 180, 175, 154, 128, 240, 39, 201, 188, 243, 177, 161, 174, 96, 125, 58, 144, 0, 7, 83, 13, 78, 35, 7, 162, 58, 2, 17, 0, 0, 0, 1, 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