← previous blocknext block →recent activity
Analyzing
Block #106,283,151
23 transactions · 22 stateful · 2026-09-19 21:22:09 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,283,151 · 23 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
2w03w16w07w18w013w114w215w316w417w018w119w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
10 touches
10 conflicts
0x1219f4e6…5013
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x66608f6c…12ad
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
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 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity