← previous blocknext block →recent activity
Analyzing
Block #98,755,065
23 transactions · 18 stateful · 2026-08-24 12:14:06 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,755,065 · 23 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
1w08w19w010w112w013w117w218w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28d7507d…de4e
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x97e4c862…4419
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x28d7507d26…2fde4e
Audit this contract →
← previous block·next block →recent activity