← previous blocknext block →recent activity
Analyzing
Block #112,486,178
32 transactions · 26 stateful · 2026-10-11 13:56:43 UTC
Parallelism
84/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,486,178 · 32 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
9w010w113w014w115w216w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0x9bf9d42d…15ae
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd58e5c6b…7188
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 0xdad20621a2…0306b1
Audit this contract →
← previous block·next block →recent activity