← previous blocknext block →recent activity
Analyzing
Block #99,199,389
17 transactions · 17 stateful · 2026-08-26 01:36:30 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,199,389 · 17 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
1w02w13w24w05w16w07w19w111w212w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8d572c…b27d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x140223cf…9ccc
0x34b655…2a6f
4 touches
1 conflict
0x6d89ee77…72bf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xfc8d572cb3…e5b27d
Audit this contract →
← previous block·next block →recent activity