← previous blocknext block →recent activity
Analyzing
Block #98,151,010
22 transactions · 20 stateful · 2026-08-22 08:58:46 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,151,010 · 22 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
1w02w03w04w18w09w110w111w015w117w218w320w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61ca6437…2142
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc4d98fb1…c354
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x61ca6437ec…412142
Audit this contract →
← previous block·next block →recent activity