← previous blocknext block →recent activity
Analyzing
Block #97,478,913
23 transactions · 22 stateful · 2026-08-20 00:09:05 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,478,913 · 23 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
2w03w14w15w07w08w19w110w214w015w217w218w319w321w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x1dc86774…166a
0x34b655…2a6f
6 touches
3 conflicts
0xb5e46043…abcd
0xa6afd3…d132
6 touches
3 conflicts
0x3e1b765a…ae54
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x75028c63…3b18
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity