← previous blocknext block →recent activity
Analyzing
Block #112,486,904
16 transactions · 16 stateful · 2026-10-11 14:00:22 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,486,904 · 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
1w02w13w24w310w011w012w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d5bad6c…76cc
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x2a0530ed…9941
0x34b655…2a6f
4 touches
1 conflict
0x3ff8e68d…bb55
0x34b655…2a6f
4 touches
1 conflict
0x46312fdc…901e
0x34b655…2a6f
4 touches
1 conflict
0x53057a6c…ce62
0x34b655…2a6f
4 touches
1 conflict
0x6f4e7625…aba5
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 0x5d5bad6ca2…2676cc
Audit this contract →
← previous block·next block →recent activity