← previous blocknext block →recent activity
Analyzing
Block #98,736,357
55 transactions · 49 stateful · 2026-08-24 10:39:54 UTC
Parallelism
71/100
Blocked
76%
Avg conflicts / tx
2.4
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,736,357 · 55 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
1w02w06w17w08w09w110w211w312w413w014w116w218w327w133w134w235w336w437w540w645w649w1051w1252w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x38963aeb…c33f
0xa6afd3…d132
12 touches
15 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
10 touches
10 conflicts
0xdb067026…9eb8
0x2b46c0…1669
10 touches
10 conflicts
0x39773cec…38ed
0xa6afd3…d132
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity