← previous blocknext block →recent activity
Analyzing
Block #96,685,626
26 transactions · 26 stateful · 2026-08-17 04:53:31 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,685,626 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w18w39w410w515w316w624w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0x890a1db9…1712
0xa6afd3…d132
6 touches
3 conflicts
0x6cb2b931…f8a7
0x34b655…2a6f
4 touches
1 conflict
0x7f9fe384…1402
0x34b655…2a6f
4 touches
1 conflict
0x8e41839a…9643
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity