← previous blocknext block →recent activity
Analyzing
Block #106,957,048
26 transactions · 25 stateful · 2026-09-22 05:54:53 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,957,048 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w013w114w015w119w222w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd349e3cd…330d
0x34b655…2a6f
6 touches
3 conflicts
0x2a46edb5…b5bd
0x99c7a7…8bf0
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xa6eca5ba…4390
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x14636d9e…78ad
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
3 conflicts on slot 0xd349e3cd2b…ae330d
Audit this contract →
← previous block·next block →recent activity