← previous blocknext block →recent activity
Analyzing
Block #112,498,118
14 transactions · 14 stateful · 2026-10-11 14:56:48 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,498,118 · 14 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
2w05w16w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x47ee9f76…8def
0x34b655…2a6f
4 touches
1 conflict
0x5cbda5eb…0590
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0xc65f46dd…513c
0x34b655…2a6f
4 touches
1 conflict
0x20166453…77f3
0x34b655…2a6f
2 touches
0 conflicts
0x68055fa2…229e
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 0x64a785e491…1c0110
Audit this contract →
← previous block·next block →recent activity