Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f10eb2f711121fac52e2960135ab9046cfda8a09cfed1af4e3800121a3bd51

Tx prefix hash: c0c6a07769fe0f1d24a391fbcf72c0f48f7469666ca74017752bdbd4479c81d4
Tx public key: a3a86251d3921bf992f4a9526f12e613b95df689891e982777d96b714fb4a9b8
Timestamp: 1735891344 Timestamp [UCT]: 2025-01-03 08:02:24 Age [y:d:h:m:s]: 00:161:20:18:12
Block: 1189198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115391 RingCT/type: yes/0
Extra: 01a3a86251d3921bf992f4a9526f12e613b95df689891e982777d96b714fb4a9b8021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5c877c57a6379245e153629b64c16b57665e8f448e5512e40fdd8401fede5e6 0.600000000000 1675703 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": 1189208, "vin": [ { "gen": { "height": 1189198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5c877c57a6379245e153629b64c16b57665e8f448e5512e40fdd8401fede5e6" } } ], "extra": [ 1, 163, 168, 98, 81, 211, 146, 27, 249, 146, 244, 169, 82, 111, 18, 230, 19, 185, 93, 246, 137, 137, 30, 152, 39, 119, 217, 107, 113, 79, 180, 169, 184, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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