← previous blocknext block →recent activity
Analyzing
Block #96,157,671
28 transactions · 27 stateful · 2026-08-15 08:37:51 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.86
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #96,157,671 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w410w511w612w713w516w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x588c5b6a…60d2
0x34b655…2a6f
6 touches
3 conflicts
0xc8f4deb0…dcf3
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity