← previous blocknext block →recent activity
Analyzing
Block #99,481,269
24 transactions · 23 stateful · 2026-08-27 01:15:26 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,481,269 · 24 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
1w02w15w06w17w29w210w111w312w213w214w317w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x922531f6…c764
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xbd22d0fc…64fd
0x34b655…2a6f
6 touches
3 conflicts
0xb9ab93a0…f656
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 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 0x922531f687…94c764
Audit this contract →
← previous block·next block →recent activity