← previous blocknext block →recent activity
Analyzing
Block #112,583,432
27 transactions · 25 stateful · 2026-10-11 22:06:03 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,583,432 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w08w19w010w111w115w019w120w221w222w323w325w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbefdde57…cd0e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8ca5006d…5941
0x34b655…2a6f
6 touches
3 conflicts
0x18a981eb…32ec
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xbefdde5725…1dcd0e
Audit this contract →
← previous block·next block →recent activity