← previous blocknext block →recent activity
Analyzing
Block #98,452,611
16 transactions · 13 stateful · 2026-08-23 10:16:08 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,452,611 · 16 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
4w06w18w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xad260a48…2584
0x34b655…2a6f
5 touches
3 conflicts
0xd7832a9d…6f9d
0x34b655…2a6f
4 touches
1 conflict
0xf8530d86…73bf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
0xb5f5f775…010b
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
6 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity