← previous blocknext block →recent activity
Analyzing
Block #97,465,804
23 transactions · 18 stateful · 2026-08-19 23:02:53 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,465,804 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w38w49w410w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xb97c885b…2933
0x34b655…2a6f
4 touches
1 conflict
0xc38a1e34…37c3
0x34b655…2a6f
4 touches
1 conflict
0x5de1fd2c…843e
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x3f4de2d1…2881
0x34b655…2a6f
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
10 conflicts on slot 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity