← previous blocknext block →recent activity
Analyzing
Block #96,601,280
23 transactions · 20 stateful · 2026-08-16 21:49:18 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,601,280 · 23 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
3w05w16w27w39w011w312w416w518w619w722w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0135ac9…730f
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xd0135ac9c4…70730f
Audit this contract →
← previous block·next block →recent activity