Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43fe227afd37c574a4334fc656e0f2876103dd6ecdcb9dbd6d6b52ebbc7edd6b

Tx prefix hash: 3e48e24d6e7473d238b59fb0599eeb689b0915b146477dda191aa3afecbd68b7
Tx public key: c45eac4f79919b3ce6da1d75e364cfa525ae6c2e659834343813f5c74e29c255
Timestamp: 1709479938 Timestamp [UCT]: 2024-03-03 15:32:18 Age [y:d:h:m:s]: 01:069:20:29:53
Block: 970345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310947 RingCT/type: yes/0
Extra: 01c45eac4f79919b3ce6da1d75e364cfa525ae6c2e659834343813f5c74e29c25502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00ced4c015483cee8bbc91f9939571fb1fc9aeee747544148414be9ad476c4e6 0.600000000000 1430196 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": 970355, "vin": [ { "gen": { "height": 970345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00ced4c015483cee8bbc91f9939571fb1fc9aeee747544148414be9ad476c4e6" } } ], "extra": [ 1, 196, 94, 172, 79, 121, 145, 155, 60, 230, 218, 29, 117, 227, 100, 207, 165, 37, 174, 108, 46, 101, 152, 52, 52, 56, 19, 245, 199, 78, 41, 194, 85, 2, 17, 0, 0, 0, 3, 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