← previous blocknext block →recent activity
Analyzing
Block #112,339,494
31 transactions · 27 stateful · 2026-10-11 01:38:43 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,339,494 · 31 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
1w04w05w16w27w39w010w115w016w117w218w321w022w123w226w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x626418b6…20b6
0x3bd359…433a
6 touches
3 conflicts
0x30c7fdeb…d657
0x34b655…2a6f
4 touches
1 conflict
0x33a13e64…4408
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
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 0xfdd40e24dd…99dca0
Audit this contract →
← previous block·next block →recent activity