← previous blocknext block →recent activity
Analyzing
Block #97,535,406
16 transactions · 14 stateful · 2026-08-20 04:53:16 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,535,406 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w08w09w213w014w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663d3288…f460
0x34b655…2a6f
8 touches
6 conflicts
0x4eb98096…65c2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd1c30e90…03a1
0x34b655…2a6f
6 touches
3 conflicts
0x588ba065…f516
0x34b655…2a6f
4 touches
1 conflict
0x68297b76…8e24
0x34b655…2a6f
4 touches
1 conflict
0x7343ac32…3e67
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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 0x663d3288e5…69f460
Audit this contract →
← previous block·next block →recent activity