Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52616360e777df33ebf3da6e8b45e4d8ca07c7fe7e6665bea3f416b60588f8df

Tx prefix hash: 281a14444725c39abf9caca3de8849c0a0fcf2ef59d5d00314664052e0e6a592
Tx public key: 8cd9c2503d020f1c13b041e55789db2c1abdddcf1e842edaf40ab657b3e08c58
Timestamp: 1697429706 Timestamp [UCT]: 2023-10-16 04:15:06 Age [y:d:h:m:s]: 01:137:05:55:10
Block: 870640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359087 RingCT/type: yes/0
Extra: 018cd9c2503d020f1c13b041e55789db2c1abdddcf1e842edaf40ab657b3e08c580211000000024b8f5122000000000000000000

1 output(s) for total of 0.800217945000 dcy

stealth address amount amount idx
00: 018dbf8a3f406662aec5a598fa83b112ab84b61d095bcf83498ad2352787bb09 0.800217945000 1325523 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": 870650, "vin": [ { "gen": { "height": 870640 } } ], "vout": [ { "amount": 800217945, "target": { "key": "018dbf8a3f406662aec5a598fa83b112ab84b61d095bcf83498ad2352787bb09" } } ], "extra": [ 1, 140, 217, 194, 80, 61, 2, 15, 28, 19, 176, 65, 229, 87, 137, 219, 44, 26, 189, 221, 207, 30, 132, 46, 218, 244, 10, 182, 87, 179, 224, 140, 88, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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