← previous blocknext block →recent activity
Analyzing
Block #112,487,282
23 transactions · 21 stateful · 2026-10-11 14:02:16 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,487,282 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w011w112w213w314w315w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51af0e92…4020
0x34b655…2a6f
8 touches
6 conflicts
0x62efa201…0a74
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x3d538e8e…702c
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
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 0x51af0e92a5…be4020
Audit this contract →
← previous block·next block →recent activity