← previous blocknext block →recent activity
Analyzing
Block #111,072,243
22 transactions · 18 stateful · 2026-10-06 15:20:55 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,072,243 · 22 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
4w07w113w019w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x262a793c…1d06
0x34b655…2a6f
4 touches
1 conflict
0xcc69885f…792f
0x30a88b…7102
2 touches
0 conflicts
0xd5d6c8dc…8045
0x30a88b…7102
2 touches
0 conflicts
0xd9d16d34…330f
0x30a88b…7102
2 touches
0 conflicts
0xdc686ec4…237e
0x30a88b…7102
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity