← previous blocknext block →recent activity
Analyzing
Block #98,670,482
20 transactions · 17 stateful · 2026-08-24 05:03:47 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,670,482 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w011w212w314w418w019w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c85c562…e29b
0x34b655…2a6f
8 touches
6 conflicts
0x074c08f8…fb56
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
6 conflicts on slot 0x0c85c56239…e9e29b
Audit this contract →
← previous block·next block →recent activity