← previous blocknext block →recent activity
Analyzing
Block #99,270,317
14 transactions · 14 stateful · 2026-08-26 07:33:26 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,270,317 · 14 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
5w06w17w28w29w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32530ce0…0a5f
0x34b655…2a6f
8 touches
6 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0xfb6148df…8609
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x2b1c1b21…6157
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 0x32530ce043…fc0a5f
Audit this contract →
← previous block·next block →recent activity