← previous blocknext block →recent activity
Analyzing
Block #112,593,892
20 transactions · 17 stateful · 2026-10-11 22:58:40 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,593,892 · 20 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
4w05w19w210w011w112w113w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4550172…3d03
0x34b655…2a6f
8 touches
6 conflicts
0xa3f09358…6cde
0x34b655…2a6f
6 touches
3 conflicts
0x625c4ed4…16aa
0x34b655…2a6f
4 touches
1 conflict
0x7a3d5e6f…7864
0x34b655…2a6f
4 touches
1 conflict
0x866110ca…7080
0x34b655…2a6f
4 touches
1 conflict
0xa7d3cb90…e1d9
0x34b655…2a6f
4 touches
1 conflict
0xadd19d1a…c0ff
0x34b655…2a6f
4 touches
1 conflict
0xbd3735d7…c973
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 0xc4550172b5…c13d03
Audit this contract →
← previous block·next block →recent activity