← previous blocknext block →recent activity
Analyzing
Block #97,397,324
17 transactions · 16 stateful · 2026-08-19 17:16:36 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,397,324 · 17 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
1w04w05w16w28w29w310w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x221a6ee3…2a3c
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x6bc293e9…556e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6f6aa736…a698
0x34b655…2a6f
4 touches
1 conflict
0xb543d97e…cc3f
0x34b655…2a6f
2 touches
0 conflicts
0xc9377f93…3739
0x34b655…2a6f
2 touches
0 conflicts
0xe181f491…f4e3
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
3 conflicts on slot 0x221a6ee3d0…b32a3c
Audit this contract →
← previous block·next block →recent activity