← previous blocknext block →recent activity
Analyzing
Block #112,485,983
20 transactions · 18 stateful · 2026-10-11 13:55:44 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,485,983 · 20 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
1w02w13w29w010w111w112w213w214w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62aca140…f539
0x34b655…2a6f
8 touches
6 conflicts
0x51af0e92…4020
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x47ccea32…8c8f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0055
0x1b6862…e19c
4 touches
1 conflict
0x17295df7…6282
0x1b6862…e19c
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 0x62aca14017…e1f539
Audit this contract →
← previous block·next block →recent activity