← previous blocknext block →recent activity
Analyzing
Block #96,093,332
18 transactions · 15 stateful · 2026-08-15 03:14:11 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,093,332 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w38w510w614w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1d820a7…23dc
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x50e616e2…8782
0x34b655…2a6f
4 touches
1 conflict
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x6e7a8a4a…105a
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
15 conflicts on slot 0xe1d820a7c4…e123dc
Audit this contract →
← previous block·next block →recent activity