← previous blocknext block →recent activity
Analyzing
Block #98,663,400
34 transactions · 33 stateful · 2026-08-24 04:26:59 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,663,400 · 34 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
1w02w07w09w010w111w212w313w414w515w016w117w218w320w422w531w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0xf9e17093…50a1
0xd32edf…ff58
11 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x46cb45de…a566
0x188d58…ea8e
8 touches
6 conflicts
0x46cb45de…a567
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
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
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity