← previous blocknext block →recent activity
Analyzing
Block #98,503,121
40 transactions · 39 stateful · 2026-08-23 14:31:27 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.63
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,503,121 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w010w111w012w114w015w117w221w323w424w527w528w630w131w536w737w839w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xb4b350eb…8c96
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…642d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 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
15 conflicts on slot 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity