← previous blocknext block →recent activity
Analyzing
Block #112,608,931
16 transactions · 14 stateful · 2026-10-12 00:14:20 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,608,931 · 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
6w09w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x2415a0e6…362e
0x34b655…2a6f
2 touches
0 conflicts
0x3c860b44…3498
0x34b655…2a6f
2 touches
0 conflicts
0x451cde3f…be3d
0x34b655…2a6f
2 touches
0 conflicts
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 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity