← previous blocknext block →recent activity
Analyzing
Block #98,066,925
23 transactions · 23 stateful · 2026-08-22 01:54:57 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,066,925 · 23 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
1w02w03w04w110w011w113w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4fd6ce…262e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xb5922b6d…5ecc
0x34b655…2a6f
4 touches
1 conflict
0xc04c372b…a87b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0xfb4fd6ce8b…d1262e
Audit this contract →
← previous block·next block →recent activity