Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9566a2b564606823137a271b4de8195b61cad9ff198a5f725e1edef2e8fc4112

Tx prefix hash: 027ac462eed3cf174e6b04ed8736b7b34612670610bf0cd1f6ce6b5b2a400ce4
Tx public key: d1c572e054c70843598bea413f6f320e642f2fa1d9acc7783a18b2e2492ab062
Timestamp: 1715364578 Timestamp [UCT]: 2024-05-10 18:09:38 Age [y:d:h:m:s]: 00:291:21:35:04
Block: 1019130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208618 RingCT/type: yes/0
Extra: 01d1c572e054c70843598bea413f6f320e642f2fa1d9acc7783a18b2e2492ab06202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0cf300c9acdeb154434602756b94d9e0f2ae7d5a252a0f97afac43b0a291e61 0.600000000000 1483017 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": 1019140, "vin": [ { "gen": { "height": 1019130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0cf300c9acdeb154434602756b94d9e0f2ae7d5a252a0f97afac43b0a291e61" } } ], "extra": [ 1, 209, 197, 114, 224, 84, 199, 8, 67, 89, 139, 234, 65, 63, 111, 50, 14, 100, 47, 47, 161, 217, 172, 199, 120, 58, 24, 178, 226, 73, 42, 176, 98, 2, 17, 0, 0, 0, 2, 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