← previous blocknext block →recent activity
Analyzing
Block #112,583,913
16 transactions · 16 stateful · 2026-10-11 22:08:28 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,583,913 · 16 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
1w05w010w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdacb24f7…56ce
0x34b655…2a6f
8 touches
6 conflicts
0x8f8f220e…d0d0
0x34b655…2a6f
6 touches
3 conflicts
0x67d00173…0d9f
0x34b655…2a6f
4 touches
1 conflict
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6235638c…643c
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
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
6 conflicts on slot 0xdacb24f781…a756ce
Audit this contract →
← previous block·next block →recent activity