← previous blocknext block →recent activity
Analyzing
Block #112,336,441
17 transactions · 16 stateful · 2026-10-11 01:23:22 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,336,441 · 17 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
5w06w110w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0xe1d9c808…b5a6
0x34b655…2a6f
4 touches
1 conflict
0xe4944062…5800
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 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity