← previous blocknext block →recent activity
Analyzing
Block #99,367,637
41 transactions · 33 stateful · 2026-08-26 15:43:14 UTC
Parallelism
59/100
Blocked
52%
Avg conflicts / tx
2.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #99,367,637 · 41 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w010w111w012w017w218w024w325w431w732w833w934w1035w1136w1237w1338w1439w1540w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xbd590df7…9891
0x34b655…2a6f
14 touches
21 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
12 touches
15 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
12 touches
15 conflicts
0xfa0c5188…06f2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity