← previous blocknext block →recent activity
Analyzing
Block #98,382,299
10 transactions · 10 stateful · 2026-08-23 04:22:23 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,382,299 · 10 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
3w04w15w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xddc9161e…15b0
0x34b655…2a6f
4 touches
1 conflict
0x972d632b…dff1
0x34b655…2a6f
3 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x750371c0…1c72
0x065c9d…c394
2 touches
0 conflicts
0x9db4ba08…91d0
0x065c9d…c394
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
3 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity