← previous blocknext block →recent activity
Analyzing
Block #98,576,261
13 transactions · 12 stateful · 2026-08-23 20:53:09 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,576,261 · 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
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0xf56d5d0e…222c
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x288fc513…d9f4
0x34b655…2a6f
2 touches
0 conflicts
0x3ca268be…8865
0x34b655…2a6f
2 touches
0 conflicts
0x485c6978…f98f
0x34b655…2a6f
2 touches
0 conflicts
0x4ccfe55c…de03
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 0xeb0b1d4366…fc9559
Audit this contract →
← previous block·next block →recent activity