← previous blocknext block →recent activity
Analyzing
Block #106,379,645
25 transactions · 21 stateful · 2026-09-20 05:27:44 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,379,645 · 25 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
1w02w13w24w35w06w18w09w110w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8cb0701…3926
0x34b655…2a6f
8 touches
6 conflicts
0xda830e9d…9484
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x78cc044a…79de
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
6 conflicts on slot 0xc8cb070152…393926
Audit this contract →
← previous block·next block →recent activity