← previous blocknext block →recent activity
Analyzing
Block #97,500,643
17 transactions · 17 stateful · 2026-08-20 01:58:23 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,500,643 · 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
2w04w05w16w27w38w09w410w512w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x330625d9…aa12
0x34b655…2a6f
12 touches
15 conflicts
0x0099420d…37b4
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
15 conflicts on slot 0x330625d975…2daa12
Audit this contract →
← previous block·next block →recent activity