← previous blocknext block →recent activity
Analyzing
Block #112,386,852
13 transactions · 12 stateful · 2026-10-11 05:36:58 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,386,852 · 13 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
1w02w13w24w05w17w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0084f08…f7ff
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb3
0x1b6862…e19c
6 touches
3 conflicts
0x2ddc3e4c…bd7c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xde5d7386…21c7
0xd32edf…ff58
5 touches
3 conflicts
0xb8394f3d…8f29
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0xa0084f0876…6af7ff
Audit this contract →
← previous block·next block →recent activity