← previous blocknext block →recent activity
Analyzing
Block #97,827,271
16 transactions · 16 stateful · 2026-08-21 05:36:00 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,827,271 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1c645adf…cd53
0x34b655…2a6f
5 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
5 touches
3 conflicts
0xb527b877…3047
0x34b655…2a6f
5 touches
3 conflicts
0xe783dfa4…549a
0x1b6862…e19c
4 touches
1 conflict
0x103e4080…0d3a
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity