← previous blocknext block →recent activity
Analyzing
Block #106,242,128
23 transactions · 19 stateful · 2026-09-19 17:55:43 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,242,128 · 23 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
2w03w110w011w112w013w114w216w219w220w321w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d81f74…f079
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0a9fcba0…98af
0x34b655…2a6f
4 touches
1 conflict
0x1ca85c58…feb2
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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 0xf0d81f7402…0af079
Audit this contract →
← previous block·next block →recent activity