← previous blocknext block →recent activity
Analyzing
Block #97,604,336
19 transactions · 19 stateful · 2026-08-20 10:42:29 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,604,336 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w210w311w412w016w517w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x94512d20…3345
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity