← previous blocknext block →recent activity
Analyzing
Block #99,038,886
11 transactions · 11 stateful · 2026-08-25 12:05:23 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,038,886 · 11 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
3w04w15w07w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8d572c…b27d
0x34b655…2a6f
6 touches
3 conflicts
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x9d22c394…c125
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x32530ce0…0a5f
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
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
3 conflicts on slot 0xfc8d572cb3…e5b27d
Audit this contract →
← previous block·next block →recent activity