← previous blocknext block →recent activity
Analyzing
Block #98,766,469
84 transactions · 52 stateful · 2026-08-24 13:11:31 UTC
Parallelism
81/100
Blocked
75%
Avg conflicts / tx
2.44
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,766,469 · 84 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w112w013w115w016w119w220w322w423w524w626w727w828w929w1033w1134w1235w1336w1437w1560w161w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x68c8d31a…d33c
0x34b655…2a6f
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xbf37bdd8…8751
0x34b655…2a6f
6 touches
3 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: 0xbb3f3cb7…74e046
120 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity