Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b542f45c2bf3d967e2ca166d7ec0d20d201dd84a19e6b68163505c4c417e40

Tx prefix hash: 8e70009b2e0f0d638d5025009f7efd82a3347941b351b3f4b8a2ed8533d2923a
Tx public key: 1d391ab0c919d1fda34b929c5859a93bb46e1f09f7261f83e3c0eb0dd2551e4a
Timestamp: 1709230876 Timestamp [UCT]: 2024-02-29 18:21:16 Age [y:d:h:m:s]: 01:252:15:15:01
Block: 968281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439279 RingCT/type: yes/0
Extra: 011d391ab0c919d1fda34b929c5859a93bb46e1f09f7261f83e3c0eb0dd2551e4a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8613b5365ffd0965f371547f39faf58dee6e22d0d8e14ce36273d403ea2c42 0.600000000000 1428088 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": 968291, "vin": [ { "gen": { "height": 968281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8613b5365ffd0965f371547f39faf58dee6e22d0d8e14ce36273d403ea2c42" } } ], "extra": [ 1, 29, 57, 26, 176, 201, 25, 209, 253, 163, 75, 146, 156, 88, 89, 169, 59, 180, 110, 31, 9, 247, 38, 31, 131, 227, 192, 235, 13, 210, 85, 30, 74, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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