← previous blocknext block →recent activity
Analyzing
Block #99,987,823
24 transactions · 21 stateful · 2026-08-28 19:59:05 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,987,823 · 24 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
7w08w19w210w013w114w216w321w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87e3f6cf…283f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x549c2377…ad00
0x34b655…2a6f
6 touches
3 conflicts
0xf61165ef…adb9
0x34b655…2a6f
6 touches
3 conflicts
0x4e62d70d…0940
0x34b655…2a6f
4 touches
1 conflict
0x4f3d15b9…3aed
0x34b655…2a6f
4 touches
1 conflict
0x61818eda…690c
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
3 conflicts on slot 0x87e3f6cf11…1d283f
Audit this contract →
← previous block·next block →recent activity