← previous blocknext block →recent activity
Analyzing
Block #98,770,036
21 transactions · 19 stateful · 2026-08-24 13:29:28 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,770,036 · 21 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
3w04w15w06w18w010w113w015w116w217w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x72d75417…809a
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xc319565b…8a57
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xf4b2a42760…660234
Audit this contract →
← previous block·next block →recent activity