← previous blocknext block →recent activity
Analyzing
Block #112,255,393
12 transactions · 11 stateful · 2026-10-10 18:35:36 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,255,393 · 12 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
5w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33738cf8…89f1
0x34b655…2a6f
8 touches
6 conflicts
0x49922a7a…7676
0x34b655…2a6f
8 touches
6 conflicts
0x502b3ee1…7f7b
0x34b655…2a6f
6 touches
3 conflicts
0x86b260e9…a3b8
0x34b655…2a6f
6 touches
3 conflicts
0x0a2131b3…455e
0x34b655…2a6f
6 touches
3 conflicts
0x27b48eab…963a
0x34b655…2a6f
6 touches
3 conflicts
0xef1de905…0582
0x34b655…2a6f
4 touches
1 conflict
0xf552fe55…17d4
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 0x33738cf892…7b89f1
Audit this contract →
← previous block·next block →recent activity