← previous blocknext block →recent activity
Analyzing
Block #98,672,021
23 transactions · 20 stateful · 2026-08-24 05:11:48 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,672,021 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w09w110w014w215w316w117w218w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb63ef486…0dcc
0x34b655…2a6f
6 touches
3 conflicts
0xe22455da…1ce1
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x87f5a1f2…35eb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x14099023…eec7
0xd32edf…ff58
5 touches
3 conflicts
0xab981df1…2941
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 0xb63ef48684…2d0dcc
Audit this contract →
← previous block·next block →recent activity