← previous blocknext block →recent activity
Analyzing
Block #99,491,619
24 transactions · 21 stateful · 2026-08-27 02:07:33 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,491,619 · 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
1w05w06w17w08w013w114w115w217w318w421w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2042b9b…0ecb
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0xfc8d572c…b27d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e59f6d5…68f0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
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 0xa2042b9b04…e00ecb
Audit this contract →
← previous block·next block →recent activity