← previous blocknext block →recent activity
Analyzing
Block #96,697,309
16 transactions · 15 stateful · 2026-08-17 05:52:17 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,697,309 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w113w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0x3610cfd5…236a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x23ef1567…8f31
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x3823a559…aaa7
0x34b655…2a6f
4 touches
1 conflict
0x39a6dd35…176e
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
6 conflicts on slot 0xe945224145…7195a3
Audit this contract →
← previous block·next block →recent activity