← previous blocknext block →recent activity
Analyzing
Block #112,492,582
24 transactions · 22 stateful · 2026-10-11 14:28:56 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,492,582 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w110w211w212w313w414w515w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x9c0f137a…e532
0x34b655…2a6f
8 touches
6 conflicts
0xc36ee521…8a07
0x34b655…2a6f
8 touches
6 conflicts
0x7102a398…272f
0x34b655…2a6f
4 touches
1 conflict
0x77815594…e3df
0x34b655…2a6f
4 touches
1 conflict
0x84bc98e3…e2b7
0x34b655…2a6f
4 touches
1 conflict
0x922e5fd2…6f68
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
10 conflicts on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity