← previous blocknext block →recent activity
Analyzing
Block #96,020,510
18 transactions · 18 stateful · 2026-08-14 21:07:54 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
2.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,020,510 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w17w28w29w310w411w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
18 touches
36 conflicts
0x00000000…000b
0x754704…b603
18 touches
36 conflicts
0x34b1e500…7687
0x754704…b603
18 touches
36 conflicts
0x00000000…000b
0x78999c…f371
18 touches
36 conflicts
0x00000000…000f
0x78999c…f371
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x004ab53c…043e
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
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: 0x00000000…7da032
36 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity