← previous blocknext block →recent activity
Analyzing
Block #115,890,270
13 transactions · 13 stateful · 2026-10-23 11:51:51 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #115,890,270 · 13 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
6w07w08w19w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2060e8f7…df8a
0x34b655…2a6f
4 touches
1 conflict
0x2ef367d0…290e
0x34b655…2a6f
4 touches
1 conflict
0x490f9242…17f1
0x34b655…2a6f
4 touches
1 conflict
0x9925086e…bf91
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
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 0x2060e8f781…93df8a
Audit this contract →
← previous block·next block →recent activity