← previous blocknext block →recent activity
Analyzing
Block #106,944,703
23 transactions · 22 stateful · 2026-09-22 04:52:44 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,944,703 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w211w312w413w114w219w321w022w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x721c4bf6…290c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
6 touches
3 conflicts
0x9619a9c7…e4f2
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
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: Perpl
10 conflicts on slot 0x721c4bf68b…24290c
Audit this contract →
← previous block·next block →recent activity