← previous blocknext block →recent activity
Analyzing
Block #98,065,044
21 transactions · 21 stateful · 2026-08-22 01:45:30 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,065,044 · 21 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
1w04w05w16w210w011w113w114w215w316w217w218w119w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
6 touches
3 conflicts
0xadbda1a7…5f21
0xa6afd3…d132
6 touches
3 conflicts
0x2a5499c6…0abf
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xaa1efc75…f3d9
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity