← previous blocknext block →recent activity
Analyzing
Block #96,695,265
17 transactions · 14 stateful · 2026-08-17 05:42:00 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,695,265 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x8047e9b2…9bb8
0x34b655…2a6f
4 touches
1 conflict
0xab96ac84…a512
0x34b655…2a6f
4 touches
1 conflict
0x6a764ba5…54b7
0x34b655…2a6f
4 touches
1 conflict
0x0aa42ae9…ed69
0x34b655…2a6f
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x5b450c7f…95ee
0x34b655…2a6f
2 touches
0 conflicts
0x75f108dc…f5a7
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x34d95d945c…603a16
Audit this contract →
← previous block·next block →recent activity