← previous blocknext block →recent activity
Analyzing
Block #98,385,438
10 transactions · 6 stateful · 2026-08-23 04:38:10 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,385,438 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x074c08f8…fb56
0x34b655…2a6f
2 touches
0 conflicts
0x0c6c7007…e8f7
0x34b655…2a6f
2 touches
0 conflicts
0x0e19799e…1a38
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9054
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9055
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity