← previous blocknext block →recent activity
Analyzing
Block #98,016,335
21 transactions · 20 stateful · 2026-08-21 21:40:15 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,016,335 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w19w011w112w113w214w015w316w417w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x8773aa7e…3ae3
0x34b655…2a6f
4 touches
1 conflict
0x8db32935…81a7
0x34b655…2a6f
4 touches
1 conflict
0x97e4c862…4419
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity