← previous blocknext block →recent activity
Analyzing
Block #112,343,067
13 transactions · 13 stateful · 2026-10-11 01:56:42 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,343,067 · 13 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
2w03w14w25w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x16c83b10…f245
0x34b655…2a6f
4 touches
1 conflict
0x317796a4…a113
0x34b655…2a6f
4 touches
1 conflict
0x4e7bf95b…91d3
0xf42df8…ad97
4 touches
1 conflict
0x100ec7e6…6b5a
0x34b655…2a6f
4 touches
1 conflict
0xb824eb68…ba97
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity