← previous blocknext block →recent activity
Analyzing
Block #96,273,210
23 transactions · 16 stateful · 2026-08-15 18:18:58 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,273,210 · 23 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
6w07w08w09w110w111w217w319w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xea1b8c07…b969
0x34b655…2a6f
8 touches
6 conflicts
0x98862f54…62ca
0x34b655…2a6f
6 touches
3 conflicts
0x6c7d4ae1…7bd3
0x34b655…2a6f
4 touches
1 conflict
0x81238469…de5d
0x34b655…2a6f
4 touches
1 conflict
0x82dd99dd…a361
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