← previous blocknext block →recent activity
Analyzing
Block #112,338,311
16 transactions · 13 stateful · 2026-10-11 01:32:46 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,338,311 · 16 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe61a16d…5ccc
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0x607973ca…5de5
0x34b655…2a6f
2 touches
0 conflicts
0x6089e57e…ae59
0x34b655…2a6f
2 touches
0 conflicts
0x7d4d87a8…07ee
0x34b655…2a6f
2 touches
0 conflicts
0xa32f6e90…9372
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 0xbe61a16d26…525ccc
Audit this contract →
← previous block·next block →recent activity