← previous blocknext block →recent activity
Analyzing
Block #96,093,710
13 transactions · 11 stateful · 2026-08-15 03:16:05 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,093,710 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9375a764…dca1
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1cc1ec8e…be2f
0x34b655…2a6f
6 touches
3 conflicts
0x26607bc2…7fd6
0x34b655…2a6f
6 touches
3 conflicts
0x6aa61057…6d06
0x34b655…2a6f
4 touches
1 conflict
0x6be98b66…e239
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x87d62b39…b5ab
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
6 conflicts on slot 0x9375a764b5…f0dca1
Audit this contract →
← previous block·next block →recent activity