← previous blocknext block →recent activity
Analyzing
Block #96,665,465
10 transactions · 7 stateful · 2026-08-17 03:12:07 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,665,465 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f5e102…b5ba
0x34b655…2a6f
6 touches
3 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xc2a783bf…25e3
0x34b655…2a6f
4 touches
1 conflict
0xea3b49a7…24d7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4850e38b…2306
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
0x34b655…2a6f
2 touches
0 conflicts
0x7a1531cd…7319
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
3 conflicts on slot 0x22f5e1024f…05b5ba
Audit this contract →
← previous block·next block →recent activity