← previous blocknext block →recent activity
Analyzing
Block #98,525,429
27 transactions · 21 stateful · 2026-08-23 16:28:00 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,525,429 · 27 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
1w03w115w016w117w223w324w425w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf6b429bb…305a
0x34b655…2a6f
4 touches
1 conflict
0xf6137c7c…e191
0x065c9d…c394
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x68531239…e9a3
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity