← previous blocknext block →recent activity
Analyzing
Block #106,216,802
26 transactions · 23 stateful · 2026-09-19 15:48:12 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,802 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w411w013w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94f4eab2…673c
0x34b655…2a6f
8 touches
6 conflicts
0x24d5eb71…ddcd
0x34b655…2a6f
8 touches
6 conflicts
0xf99856c4…370d
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x94f4eab25f…91673c
Audit this contract →
← previous block·next block →recent activity