← previous blocknext block →recent activity
Analyzing
Block #98,655,402
20 transactions · 17 stateful · 2026-08-24 03:45:11 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,655,402 · 20 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
1w03w15w011w112w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b16dd0…0426
0x34b655…2a6f
6 touches
3 conflicts
0xb63ef486…0dcc
0x34b655…2a6f
6 touches
3 conflicts
0x29ab4ba1…2696
0x34b655…2a6f
4 touches
1 conflict
0x340e493d…4f65
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x8e521e54…a2ff
0x34b655…2a6f
4 touches
1 conflict
0x8f3cbbac…455a
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 0xb7b16dd022…c80426
Audit this contract →
← previous block·next block →recent activity