← previous blocknext block →recent activity
Analyzing
Block #98,654,755
25 transactions · 21 stateful · 2026-08-24 03:41:47 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,654,755 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w113w214w316w417w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73223e6d…ed70
0x34b655…2a6f
8 touches
6 conflicts
0xb63ef486…0dcc
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xe31cf99d…cb66
0x754704…b603
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 0x73223e6d8f…a4ed70
Audit this contract →
← previous block·next block →recent activity