← previous blocknext block →recent activity

Analyzing

Block #106,565,748

17 transactions · 17 stateful · 2026-09-20 21:04:24 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,565,748  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x7c925651…2372

0x34b655…2a6f

6 touches
3 conflicts

0x2aab0897…78f7

0x34b655…2a6f

6 touches
3 conflicts

0x5315d42e…e240

0x34b655…2a6f

6 touches
3 conflicts

0x76ed8777…1e5f

0x34b655…2a6f

4 touches
1 conflict

0x9dd0a735…4d04

0x34b655…2a6f

4 touches
1 conflict

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0x20b1228b…2487

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x80c74517…647210

3 conflicts on slot 0x0000000000…00004c

← previous block·next block →recent activity