← previous blocknext block →recent activity
Analyzing
Block #112,379,622
8 transactions · 7 stateful · 2026-10-11 05:00:36 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,379,622 · 8 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
2w03w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0e3d365e…df2a
0x34b655…2a6f
2 touches
0 conflicts
0x1b5989b4…4dbf
0x34b655…2a6f
2 touches
0 conflicts
0x1cc89ad2…8e02
0x34b655…2a6f
2 touches
0 conflicts
0x248c4abe…a927
0x34b655…2a6f
2 touches
0 conflicts
0x30c7fdeb…d657
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity