← previous blocknext block →recent activity
Analyzing
Block #96,665,287
16 transactions · 14 stateful · 2026-08-17 03:11:14 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,665,287 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w09w210w311w414w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ee5c07b…7eb9
0x34b655…2a6f
6 touches
3 conflicts
0xed324c8e…b866
0x34b655…2a6f
6 touches
3 conflicts
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x21170416…c384
0x34b655…2a6f
4 touches
1 conflict
0x2ba6089f…407f
0x34b655…2a6f
4 touches
1 conflict
0x4850e38b…2306
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x2ee5c07b21…237eb9
Audit this contract →
← previous block·next block →recent activity