Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eebdde833bf3630569d8413210adcdd6f04f5ce62c38c341f24a4960591c0eb7

Tx prefix hash: 368a38d69b170edd6d15e52dbac0e670247bf73feb060435a5bc471db3852e23
Tx public key: e5d3fd6c27f3f1c2bc005dec48ac5f16e77f39af97ce9bffd01fefb99f480a6a
Timestamp: 1705206509 Timestamp [UCT]: 2024-01-14 04:28:29 Age [y:d:h:m:s]: 01:300:20:19:26
Block: 934888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473843 RingCT/type: yes/0
Extra: 01e5d3fd6c27f3f1c2bc005dec48ac5f16e77f39af97ce9bffd01fefb99f480a6a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fc7e69559bd1c83f35e87766b55a2e869ec75c4dc3ef7a1f3c09a72cc20978f 0.600000000000 1392904 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": 934898, "vin": [ { "gen": { "height": 934888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fc7e69559bd1c83f35e87766b55a2e869ec75c4dc3ef7a1f3c09a72cc20978f" } } ], "extra": [ 1, 229, 211, 253, 108, 39, 243, 241, 194, 188, 0, 93, 236, 72, 172, 95, 22, 231, 127, 57, 175, 151, 206, 155, 255, 208, 31, 239, 185, 159, 72, 10, 106, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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