← previous blocknext block →recent activity
Analyzing
Block #98,097,368
22 transactions · 21 stateful · 2026-08-22 04:28:09 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,097,368 · 22 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
1w02w04w15w06w28w09w010w115w216w317w418w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x97f6628b…99c9
0x34b655…2a6f
8 touches
6 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0xad862891…5d02
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x73dbec8c…fa7b
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity