← previous blocknext block →recent activity
Analyzing
Block #99,308,142
87 transactions · 58 stateful · 2026-08-26 10:43:42 UTC
Parallelism
78/100
Blocked
86%
Avg conflicts / tx
2.97
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #99,308,142 · 87 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w29w023w124w226w227w328w429w530w631w732w837w943w1044w348w449w550w651w152w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x38963aeb…c33f
0xa6afd3…d132
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0xc8ab31f9…8ce9
0xa6afd3…d132
18 touches
36 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
16 touches
28 conflicts
0x5778d110…d2e6
0xc8689a…ee79
14 touches
21 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
14 touches
21 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity