← previous blocknext block →recent activity
Analyzing
Block #98,260,501
26 transactions · 22 stateful · 2026-08-22 18:09:36 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,260,501 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w06w17w28w09w111w013w117w220w223w024w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1e1bee47…1efa
0x34b655…2a6f
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51a9c528…d9c3
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
3 conflicts on slot 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity