← previous blocknext block →recent activity
Analyzing
Block #98,015,060
24 transactions · 21 stateful · 2026-08-21 21:33:50 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,015,060 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w08w19w210w320w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x6d8ad688…4bf5
0xa6afd3…d132
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0xad3ef711…4f2b
0x2b46c0…1669
8 touches
6 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
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: 0xbb3f3cb7…74e046
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity