← previous blocknext block →recent activity
Analyzing
Block #98,672,852
20 transactions · 18 stateful · 2026-08-24 05:16:06 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,672,852 · 20 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
1w02w03w14w06w07w18w110w113w214w315w418w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x05395f24…9ad8
0x34b655…2a6f
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
4 touches
1 conflict
0x1a6c1a40…114e
0x34b655…2a6f
4 touches
1 conflict
0x2cef1eff…9f14
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x61bc6883…e4cb
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity