← previous blocknext block →recent activity
Analyzing
Block #97,359,803
43 transactions · 39 stateful · 2026-08-19 13:45:43 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
2.26
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,359,803 · 43 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w010w111w112w214w115w122w323w425w227w529w630w731w832w933w934w1036w1039w1141w1342w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x22e2bbb6…2720
0x34b655…2a6f
12 touches
15 conflicts
0xab924b05…e1b6
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
10 touches
10 conflicts
0x12cae920…cbc9
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
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
45 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity