← previous blocknext block →recent activity
Analyzing
Block #98,648,169
15 transactions · 14 stateful · 2026-08-24 03:07:20 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,648,169 · 15 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
1w02w16w27w011w012w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0x9e581536…09ba
0x34b655…2a6f
4 touches
1 conflict
0xc2403164…b6d3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity