← previous blocknext block →recent activity
Analyzing
Block #112,235,962
8 transactions · 7 stateful · 2026-10-10 16:57:50 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,235,962 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d6f9eb7…f2a2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x210fbc04…9b0e
0x34b655…2a6f
2 touches
0 conflicts
0x428aab15…334a
0x34b655…2a6f
2 touches
0 conflicts
0x49d4e4d8…72c3
0x34b655…2a6f
2 touches
0 conflicts
0x4a4715ab…840b
0x34b655…2a6f
2 touches
0 conflicts
0x4bdc4b94…fc2c
0x34b655…2a6f
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 0x9d6f9eb721…79f2a2
Audit this contract →
← previous block·next block →recent activity