← previous blocknext block →recent activity
Analyzing
Block #112,341,509
18 transactions · 16 stateful · 2026-10-11 01:48:51 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,341,509 · 18 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
2w03w15w06w18w210w111w315w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44eee1e7…3b34
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1411c340…19c8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb8f43c8d…77b2
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…6437
0x1b6862…e19c
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
3 conflicts on slot 0x44eee1e7fa…2b3b34
Audit this contract →
← previous block·next block →recent activity