← previous blocknext block →recent activity
Analyzing
Block #97,362,625
21 transactions · 18 stateful · 2026-08-19 14:00:22 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,362,625 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w19w210w313w414w517w018w119w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xf3383813…4a0c
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0xbc2413c7…b4c2
0x34b655…2a6f
6 touches
3 conflicts
0x5cd36012…d89a
0x34b655…2a6f
4 touches
1 conflict
0x62efcbc7…c7e7
0x34b655…2a6f
4 touches
1 conflict
0x671560e4…1c4f
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity