← previous blocknext block →recent activity
Analyzing
Block #98,733,395
47 transactions · 43 stateful · 2026-08-24 10:25:00 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
2.17
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,733,395 · 47 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w07w09w110w011w012w113w114w015w120w021w123w124w025w126w227w328w431w135w137w338w439w540w641w742w843w944w1045w1146w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x4b25d5ba…ab7a
0x40c49f…2af0
11 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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