← previous blocknext block →recent activity
Analyzing
Block #98,103,331
73 transactions · 56 stateful · 2026-08-22 04:58:09 UTC
Parallelism
79/100
Blocked
61%
Avg conflicts / tx
2.19
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #98,103,331 · 73 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w27w08w121w022w024w125w226w027w030w131w232w333w434w537w439w540w642w143w145w246w347w448w559w472w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x261cbea7…e35d
0x34b655…2a6f
10 touches
10 conflicts
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x62910921…3016
0x34b655…2a6f
10 touches
10 conflicts
0x523de645…4f58
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity