Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d451db5fb904fc204361357169b0ae4269201cfcc638c4a2882d271a1fcd759

Tx prefix hash: 7371158bb611f6c3681f66f4e7e066950c9ee4fa39a6a70b0d75565279d15da4
Tx public key: c32a003cad8e6eff03d0d26ca5e66995e00761a5c2aa3d3b4c9a4e0e59e5679a
Timestamp: 1694714745 Timestamp [UCT]: 2023-09-14 18:05:45 Age [y:d:h:m:s]: 01:201:09:00:18
Block: 848112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405006 RingCT/type: yes/0
Extra: 01c32a003cad8e6eff03d0d26ca5e66995e00761a5c2aa3d3b4c9a4e0e59e5679a02110000000133af99f4000000000000000000

1 output(s) for total of 0.950282946000 dcy

stealth address amount amount idx
00: 8e1436f447d6d6b5049bcde3e3ee3b8f40e7506f3a1a9b56af893df2c54bb86e 0.950282946000 1301696 of 0

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": 848122, "vin": [ { "gen": { "height": 848112 } } ], "vout": [ { "amount": 950282946, "target": { "key": "8e1436f447d6d6b5049bcde3e3ee3b8f40e7506f3a1a9b56af893df2c54bb86e" } } ], "extra": [ 1, 195, 42, 0, 60, 173, 142, 110, 255, 3, 208, 210, 108, 165, 230, 105, 149, 224, 7, 97, 165, 194, 170, 61, 59, 76, 154, 78, 14, 89, 229, 103, 154, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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