← previous blocknext block →recent activity
Analyzing
Block #98,418,986
10 transactions · 10 stateful · 2026-08-23 07:26:58 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,418,986 · 10 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
5w06w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16ffb3d…fe01
0x34b655…2a6f
6 touches
3 conflicts
0xe75a2823…7960
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x065a7c9d…5c30
0x34b655…2a6f
2 touches
0 conflicts
0x1077e423…e3f8
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
3 conflicts on slot 0xd16ffb3db8…81fe01
Audit this contract →
← previous block·next block →recent activity