← previous blocknext block →recent activity
Analyzing
Block #97,685,483
20 transactions · 20 stateful · 2026-08-20 17:39:13 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,685,483 · 20 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
1w02w14w05w16w27w28w39w010w011w113w215w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe70f6c1d…2539
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf504c9e0…be9c
0x34b655…2a6f
4 touches
1 conflict
0x43371829…f8f0
0xa6afd3…d132
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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 0xe70f6c1de1…fc2539
Audit this contract →
← previous block·next block →recent activity