← previous blocknext block →recent activity
Analyzing
Block #106,199,073
19 transactions · 17 stateful · 2026-09-19 14:18:55 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,199,073 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w29w310w411w512w013w115w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3e4a8cc…4cee
0x34b655…2a6f
10 touches
10 conflicts
0xb550abea…2729
0x34b655…2a6f
8 touches
6 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6274ade5…fea0
0x34b655…2a6f
6 touches
3 conflicts
0x03500bec…db28
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: Perpl
10 conflicts on slot 0xd3e4a8ccdf…e74cee
Audit this contract →
← previous block·next block →recent activity