← previous blocknext block →recent activity
Analyzing
Block #112,486,106
11 transactions · 11 stateful · 2026-10-11 13:56:21 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,486,106 · 11 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7102a398…272f
0x34b655…2a6f
4 touches
1 conflict
0xdad20621…06b1
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0x2ae2b5fd…1e43
0x34b655…2a6f
2 touches
0 conflicts
0x35eab2e5…3c0a
0x34b655…2a6f
2 touches
0 conflicts
0x92b24e8a…1afa
0x34b655…2a6f
2 touches
0 conflicts
0x9c4c9466…a4e3
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 0x775a8ad3ca…e38307
Audit this contract →
← previous block·next block →recent activity