← previous blocknext block →recent activity
Analyzing
Block #98,764,917
21 transactions · 18 stateful · 2026-08-24 13:03:43 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,764,917 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w512w514w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x059e0ac0…0267
0x34b655…2a6f
6 touches
3 conflicts
0x2a949bb2…8769
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x5d137145…d8d9
0x34b655…2a6f
4 touches
1 conflict
0x61818eda…690c
0x34b655…2a6f
4 touches
1 conflict
0x6951cc6a…e839
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity