← previous blocknext block →recent activity
Analyzing
Block #111,842,369
15 transactions · 12 stateful · 2026-10-09 07:57:29 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,842,369 · 15 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
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x2ef367d0…290e
0x34b655…2a6f
2 touches
0 conflicts
0x4c23a35d…873a
0x34b655…2a6f
2 touches
0 conflicts
0x5afb4b3e…bbdf
0x34b655…2a6f
2 touches
0 conflicts
0x5ed7be90…e66b
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 0x36a76bd264…b01fb0
Audit this contract →
← previous block·next block →recent activity