← previous blocknext block →recent activity
Analyzing
Block #99,483,832
20 transactions · 20 stateful · 2026-08-27 01:28:21 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,483,832 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w310w011w112w214w315w416w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x931975c2…b7b3
0x34b655…2a6f
8 touches
6 conflicts
0x733c7779…a647
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3ad04ce1…1904
0xa6afd3…d132
6 touches
3 conflicts
0x586b9498…a2cc
0x34b655…2a6f
6 touches
3 conflicts
0x649a7992…d294
0x34b655…2a6f
5 touches
3 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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity