← previous blocknext block →recent activity
Analyzing
Block #106,952,253
20 transactions · 18 stateful · 2026-09-22 05:30:45 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,952,253 · 20 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
2w05w110w211w312w415w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627ccb46…b58f
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0x67287ef9…2d07
0x34b655…2a6f
6 touches
3 conflicts
0x6a14baa3…c6e9
0x34b655…2a6f
6 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
6 conflicts on slot 0x627ccb4662…32b58f
Audit this contract →
← previous block·next block →recent activity