← previous blocknext block →recent activity
Analyzing
Block #98,674,796
44 transactions · 38 stateful · 2026-08-24 05:26:13 UTC
Parallelism
68/100
Blocked
66%
Avg conflicts / tx
2.48
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,674,796 · 44 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w211w312w013w114w015w117w218w019w121w022w123w228w132w233w334w435w537w738w839w940w1042w1243w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x81ceb686…4df3
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity