← previous blocknext block →recent activity
Analyzing
Block #98,505,293
180 transactions · 70 stateful · 2026-08-23 14:42:42 UTC
Parallelism
89/100
Blocked
83%
Avg conflicts / tx
2.24
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,505,293 · 180 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
1w02w13w25w36w47w514w816w357w458w559w660w761w862w963w1064w1165w1266w13152w9154w10159w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
38 touches
171 conflicts
0x889d5e90…929a
0x2a68ba…90c5
28 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
26 touches
78 conflicts
0x5778d110…d2e6
0xc8689a…ee79
26 touches
78 conflicts
0x40970e69…da50
0x2b46c0…1669
24 touches
66 conflicts
0x55012d1a…3907
0x2b46c0…1669
22 touches
55 conflicts
0x56a919c4…ab49
0xee8c0e…1242
22 touches
55 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: 0x681e908b…e1ae09
171 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity