← previous blocknext block →recent activity
Analyzing
Block #96,020,658
30 transactions · 30 stateful · 2026-08-14 21:08:39 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
2.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,020,658 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w312w116w417w518w619w720w823w924w225w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56153262…21ce
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xfd4a5ef1…e4c4
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
8 touches
6 conflicts
0x1a5d321d…a474
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x5615326245…a221ce
Audit this contract →
← previous block·next block →recent activity