← previous blocknext block →recent activity
Analyzing
Block #96,618,935
11 transactions · 9 stateful · 2026-08-16 23:18:06 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,618,935 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfd33a92…5c35
0x34b655…2a6f
10 touches
10 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2bfc672f…4d28
0x34b655…2a6f
6 touches
3 conflicts
0xa8007f99…116c
0x34b655…2a6f
4 touches
3 conflicts
0x5ef8a7e4…9f90
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 0xbfd33a920c…0a5c35
Audit this contract →
← previous block·next block →recent activity