← previous blocknext block →recent activity
Analyzing
Block #112,246,685
24 transactions · 22 stateful · 2026-10-10 17:51:47 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,246,685 · 24 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
6w07w19w010w112w013w115w016w117w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4550172…3d03
0x34b655…2a6f
8 touches
6 conflicts
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x22badbc6…4c24
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x6324ccc9…14fd
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 0xc4550172b5…c13d03
Audit this contract →
← previous block·next block →recent activity