← previous blocknext block →recent activity
Analyzing
Block #98,260,879
53 transactions · 45 stateful · 2026-08-22 18:11:30 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.7
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #98,260,879 · 53 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w19w012w213w115w016w118w219w322w023w226w027w030w134w135w338w439w442w548w1050w1251w1352w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
14 touches
21 conflicts
0x3e49348b…9445
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca0fef1c…b548
0x34b655…2a6f
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
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: Perpl
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity