← previous blocknext block →recent activity
Analyzing
Block #98,664,027
18 transactions · 17 stateful · 2026-08-24 04:30:13 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,664,027 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w012w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd5c557…de1e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x00f19757…9252
0x34b655…2a6f
2 touches
0 conflicts
0x05395f24…9ad8
0x34b655…2a6f
2 touches
0 conflicts
0x10f0a1bf…12c3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0bd5c55710…26de1e
Audit this contract →
← previous block·next block →recent activity