← previous blocknext block →recent activity
Analyzing
Block #97,673,971
18 transactions · 18 stateful · 2026-08-20 16:40:22 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,673,971 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w27w08w19w013w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x157b6348…8604
0x34b655…2a6f
6 touches
3 conflicts
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xe429e4c9…9510
0x34b655…2a6f
4 touches
1 conflict
0x1eec16a0…9e8c
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
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
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity