← previous blocknext block →recent activity
Analyzing
Block #98,667,512
54 transactions · 52 stateful · 2026-08-24 04:48:20 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
3.31
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,667,512 · 54 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w210w114w115w216w317w418w519w322w427w340w143w545w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity