← previous blocknext block →recent activity
Analyzing
Block #96,282,977
19 transactions · 18 stateful · 2026-08-15 19:08:05 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,282,977 · 19 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
2w03w14w06w17w28w39w410w512w413w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x643fb585…0fd0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
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 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity