Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e4026716e67044db4bbc18769eeb3a94b321f6a2618543fc5822c7965bc4f0

Tx prefix hash: e30444eae82a4791323c45d12bec3d1e328a4e4fffe6f7ffa990d475fb7444ea
Tx public key: 5d033e6a94eab78ca33e56fbd238c97e8b0cf83ba6eb40402a45ede529ba9bd0
Timestamp: 1733649985 Timestamp [UCT]: 2024-12-08 09:26:25 Age [y:d:h:m:s]: 00:116:21:48:46
Block: 1170626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83345 RingCT/type: yes/0
Extra: 015d033e6a94eab78ca33e56fbd238c97e8b0cf83ba6eb40402a45ede529ba9bd0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d51e8f4530e621fc007658fe7807e09fd77b4a56c8ae8ec0bd55ab5d07d44e31 0.600000000000 1656357 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": 1170636, "vin": [ { "gen": { "height": 1170626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d51e8f4530e621fc007658fe7807e09fd77b4a56c8ae8ec0bd55ab5d07d44e31" } } ], "extra": [ 1, 93, 3, 62, 106, 148, 234, 183, 140, 163, 62, 86, 251, 210, 56, 201, 126, 139, 12, 248, 59, 166, 235, 64, 64, 42, 69, 237, 229, 41, 186, 155, 208, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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