← previous blocknext block →recent activity
Analyzing
Block #96,783,592
16 transactions · 14 stateful · 2026-08-17 13:06:15 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,783,592 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w010w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf67dab35…5381
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xacd1b162…bee6
0x34b655…2a6f
8 touches
6 conflicts
0x28f324ed…9db7
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0xe4f5cdcb…d942
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
10 conflicts on slot 0xf67dab35c4…ea5381
Audit this contract →
← previous block·next block →recent activity