← previous blocknext block →recent activity
Analyzing
Block #112,526,216
19 transactions · 17 stateful · 2026-10-11 17:18:10 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,526,216 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w211w012w013w114w115w216w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x464a82ff…41de
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x5c8e7687…d8bd
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xaa67b1e8…93e4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x464a82ff2d…8a41de
Audit this contract →
← previous block·next block →recent activity