← previous blocknext block →recent activity
Analyzing
Block #97,558,708
35 transactions · 27 stateful · 2026-08-20 06:51:25 UTC
Parallelism
91/100
Blocked
37%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,558,708 · 35 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w210w011w113w014w015w016w119w122w023w127w229w130w134w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x397bf298…20ec
0x34b655…2a6f
6 touches
3 conflicts
0xd643eb6a…453c
0xd32edf…ff58
5 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x24ed74ea…a3ff
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
3 conflicts on slot 0x397bf2980c…2620ec
Audit this contract →
← previous block·next block →recent activity