← previous blocknext block →recent activity
Analyzing
Block #112,591,533
11 transactions · 11 stateful · 2026-10-11 22:46:48 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,591,533 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0668f0f…ce1d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x40b03d8c…6ebe
0x34b655…2a6f
4 touches
1 conflict
0x5160ddaf…ebd5
0x34b655…2a6f
4 touches
1 conflict
0x5e907887…cbeb
0x34b655…2a6f
4 touches
1 conflict
0xae74dc9c…a463
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…643c
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb86
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
1 conflict on slot 0xf0668f0f51…4cce1d
Audit this contract →
← previous block·next block →recent activity