← previous blocknext block →recent activity
Analyzing
Block #97,732,343
30 transactions · 20 stateful · 2026-08-20 21:36:54 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,732,343 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w110w014w015w118w021w222w324w125w226w327w428w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x38a6a1f1…0e07
0xd32edf…ff58
7 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4f7e6197…548f
0x34b655…2a6f
4 touches
1 conflict
0xb0ef7740…e06d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity