← previous blocknext block →recent activity
Analyzing
Block #112,485,312
23 transactions · 22 stateful · 2026-10-11 13:52:22 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,485,312 · 23 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
3w04w16w07w115w219w320w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbd9f2cb…e85e
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x92b24e8a…1afa
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
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
3 conflicts on slot 0xfbd9f2cb97…33e85e
Audit this contract →
← previous block·next block →recent activity