← previous blocknext block →recent activity
Analyzing
Block #112,583,912
19 transactions · 16 stateful · 2026-10-11 22:08:28 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,583,912 · 19 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
6w07w110w011w112w214w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd89d2a92…75aa
0x34b655…2a6f
8 touches
6 conflicts
0xdacb24f7…56ce
0x34b655…2a6f
6 touches
3 conflicts
0xec32daae…2cc6
0x34b655…2a6f
4 touches
1 conflict
0xffbb7b61…d0e0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x41439da9…7904
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
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 0xd89d2a92d4…4575aa
Audit this contract →
← previous block·next block →recent activity