← previous blocknext block →recent activity
Analyzing
Block #105,844,131
14 transactions · 14 stateful · 2026-09-18 08:31:30 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,844,131 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xa62eb46f…89b1
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x24574ba3…6505
0x34b655…2a6f
2 touches
0 conflicts
0x36f861c9…24fd
0x34b655…2a6f
2 touches
0 conflicts
0x7c216fca…20cb
0x34b655…2a6f
2 touches
0 conflicts
0x89143d37…17d6
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6c7c1a4b7d…d35751
Audit this contract →
← previous block·next block →recent activity