← previous blocknext block →recent activity
Analyzing
Block #98,929,177
54 transactions · 48 stateful · 2026-08-25 02:50:18 UTC
Parallelism
63/100
Blocked
73%
Avg conflicts / tx
3.13
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,929,177 · 54 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w17w08w19w210w311w430w531w641w742w843w944w1048w1453w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x3ad04ce1…1904
0xa6afd3…d132
10 touches
10 conflicts
0xb71f7e11…d40e
0x2b46c0…1669
8 touches
6 conflicts
0xdeed550b…338b
0x2b46c0…1669
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3187fda9…57d9
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity