← previous blocknext block →recent activity
Analyzing
Block #97,604,992
20 transactions · 19 stateful · 2026-08-20 10:45:47 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,604,992 · 20 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
2w03w04w15w16w27w38w39w410w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x40ac662f…df77
0x34b655…2a6f
8 touches
6 conflicts
0xe6bc2705…d15b
0x34b655…2a6f
4 touches
1 conflict
0x214dc988…ba27
0x34b655…2a6f
4 touches
1 conflict
0x62811193…186d
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
0x2b46c0…1669
2 touches
0 conflicts
0x7a89325a…d7e0
0x2b46c0…1669
2 touches
0 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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity