← previous blocknext block →recent activity
Analyzing
Block #98,734,043
17 transactions · 16 stateful · 2026-08-24 10:28:16 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,734,043 · 17 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
3w04w15w26w07w18w39w410w512w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2be3eb33…2ee3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x2be3eb337e…d22ee3
Audit this contract →
← previous block·next block →recent activity