Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c8a66c18ba935dea234b1756377d709a4db290bbda9805f39b6d0e2db0d902

Tx prefix hash: 2600a639050cec16f416a5bf7ab01695d832f20b815a7693a8388da4c73cbf7a
Tx public key: 05ff6a7c1816387945784893f70366b3a410b02e74a9e9d3548a0e0fddf1e4cc
Timestamp: 1715331205 Timestamp [UCT]: 2024-05-10 08:53:25 Age [y:d:h:m:s]: 00:292:05:54:28
Block: 1018855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208865 RingCT/type: yes/0
Extra: 0105ff6a7c1816387945784893f70366b3a410b02e74a9e9d3548a0e0fddf1e4cc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f210fc4d13ef0010cc5d3b8fcfbcd40aa0f4b0ec1e6032fb737a4323e957404 0.600000000000 1482650 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": 1018865, "vin": [ { "gen": { "height": 1018855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f210fc4d13ef0010cc5d3b8fcfbcd40aa0f4b0ec1e6032fb737a4323e957404" } } ], "extra": [ 1, 5, 255, 106, 124, 24, 22, 56, 121, 69, 120, 72, 147, 247, 3, 102, 179, 164, 16, 176, 46, 116, 169, 233, 211, 84, 138, 14, 15, 221, 241, 228, 204, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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