← previous blocknext block →recent activity
Analyzing
Block #98,736,289
17 transactions · 12 stateful · 2026-08-24 10:39:33 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,736,289 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w19w210w311w412w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfffefeb2…ee44
0x40c49f…2af0
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
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
15 conflicts on slot 0xfffefeb2f0…dbee44
Audit this contract →
← previous block·next block →recent activity