← previous blocknext block →recent activity
Analyzing
Block #112,492,432
25 transactions · 21 stateful · 2026-10-11 14:28:11 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
0.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #112,492,432 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w310w011w112w113w214w316w417w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x70af8a92…5ded
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
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