← previous blocknext block →recent activity
Analyzing
Block #98,452,487
16 transactions · 14 stateful · 2026-08-23 10:15:31 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,452,487 · 16 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
2w07w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfedf4e1d…bf05
0x34b655…2a6f
4 touches
1 conflict
0xc4d98fb1…c354
0x40c49f…2af0
4 touches
1 conflict
0xc4015074…e9f6
0x34b655…2a6f
4 touches
1 conflict
0x21e8ab54…3b4b
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
2 touches
0 conflicts
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x72f046e0…ed7d
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 0xfedf4e1d35…bcbf05
Audit this contract →
← previous block·next block →recent activity