← previous blocknext block →recent activity
Analyzing
Block #112,171,611
24 transactions · 22 stateful · 2026-10-10 11:34:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,171,611 · 24 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
1w03w17w08w19w210w011w114w015w118w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2f1388fc…4885
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7954ece9…fef0
0x34b655…2a6f
6 touches
3 conflicts
0xbbefaf45…1618
0x34b655…2a6f
4 touches
1 conflict
0x9b281361…7a56
0x34b655…2a6f
4 touches
1 conflict
0x5d08f20a…d210
0x34b655…2a6f
4 touches
1 conflict
0x6e831143…b588
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity