← previous blocknext block →recent activity
Analyzing
Block #96,284,490
17 transactions · 16 stateful · 2026-08-15 19:15:42 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,284,490 · 17 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
3w04w07w19w010w211w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
10 touches
10 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x14eb2f47…8a2e
0x34b655…2a6f
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
6 touches
3 conflicts
0x7fa44fe8…484e
0x34b655…2a6f
6 touches
3 conflicts
0x312e9622…f814
0x34b655…2a6f
4 touches
1 conflict
0x3c8d99a5…b937
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity