← previous blocknext block →recent activity
Analyzing
Block #98,571,012
13 transactions · 12 stateful · 2026-08-23 20:25:47 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,571,012 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x45e0cbdf…e991
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x716abb51…7ecf
0x34b655…2a6f
4 touches
1 conflict
0x2c97e962…ce1d
0x34b655…2a6f
2 touches
0 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
2 touches
0 conflicts
0x6347a8f1…d73e
0x34b655…2a6f
2 touches
0 conflicts
0x699c6386…f7ba
0x34b655…2a6f
2 touches
0 conflicts
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity