← previous blocknext block →recent activity
Analyzing
Block #97,355,325
22 transactions · 22 stateful · 2026-08-19 13:22:36 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,355,325 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w09w111w112w014w215w016w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18906a6…d2e3
0x34b655…2a6f
8 touches
6 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
6 conflicts on slot 0xf18906a60b…97d2e3
Audit this contract →
← previous block·next block →recent activity