← previous blocknext block →recent activity
Analyzing
Block #97,553,281
20 transactions · 18 stateful · 2026-08-20 06:23:42 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,553,281 · 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
1w02w13w04w05w16w27w38w39w412w513w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c91855…d0df
0x34b655…2a6f
8 touches
6 conflicts
0xeb1dd5ad…69d1
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xa3c9185504…b5d0df
Audit this contract →
← previous block·next block →recent activity