← previous blocknext block →recent activity
Analyzing
Block #98,569,327
98 transactions · 78 stateful · 2026-08-23 20:16:58 UTC
Parallelism
77/100
Blocked
73%
Avg conflicts / tx
2.67
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,569,327 · 98 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w636w437w538w641w842w964w1165w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0x00000000…0003
0x019883…2a9a
14 touches
21 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
14 touches
21 conflicts
0x00000000…0000
0x019883…2a9a
14 touches
21 conflicts
0x00000000…0002
0x019883…2a9a
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xa10c86f8…4b74
0x3bd359…433a
14 touches
21 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity