← previous blocknext block →recent activity
Analyzing
Block #98,988,603
59 transactions · 41 stateful · 2026-08-25 07:49:17 UTC
Parallelism
78/100
Blocked
76%
Avg conflicts / tx
1.41
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,988,603 · 59 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
1w02w03w14w27w08w123w224w325w429w230w331w432w533w638w145w147w951w353w754w856w1057w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xd1203697…1ae0
0x40c49f…2af0
10 touches
10 conflicts
0xd08db6ee…a943
0x40c49f…2af0
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd69c8efa…4ea1
0x34b655…2a6f
8 touches
6 conflicts
0x3a921be0…779c
0x2a68ba…90c5
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: 0x40c49f17…d22af0
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity