← previous blocknext block →recent activity
Analyzing
Block #98,065,938
17 transactions · 17 stateful · 2026-08-22 01:49:59 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,065,938 · 17 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
2w05w08w09w110w011w113w214w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad370487…86e2
0x34b655…2a6f
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x47719139…f64d
0x34b655…2a6f
4 touches
1 conflict
0x614da1af…3ad5
0x34b655…2a6f
4 touches
1 conflict
0x8b82e18a…4345
0x34b655…2a6f
4 touches
1 conflict
0x93bfd5d2…4a46
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 0xad370487fc…c486e2
Audit this contract →
← previous block·next block →recent activity