← previous blocknext block →recent activity
Analyzing
Block #98,068,263
27 transactions · 19 stateful · 2026-08-22 02:01:41 UTC
Parallelism
93/100
Blocked
21%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,068,263 · 27 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
1w07w013w015w119w021w123w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x69bf73eb…fe40
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x83fc4fc1…6fe1
0x2b46c0…1669
2 touches
0 conflicts
0xce1efe70…2ec8
0x2b46c0…1669
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity