← previous blocknext block →recent activity
Analyzing
Block #98,479,544
13 transactions · 13 stateful · 2026-08-23 12:32:00 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,479,544 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30908823…a62d
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4d8b1dbf…afff
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x155e52ca…fac7
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 0x3090882336…22a62d
Audit this contract →
← previous block·next block →recent activity