← previous blocknext block →recent activity
Analyzing
Block #96,318,357
10 transactions · 10 stateful · 2026-08-15 22:06:02 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,318,357 · 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
4w05w16w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5f3026c…9423
0x968279…9342
6 touches
3 conflicts
0xd5f3026c…9424
0x968279…9342
6 touches
3 conflicts
0xd5f3026c…9427
0x968279…9342
6 touches
3 conflicts
0xd5f3026c…9428
0x968279…9342
6 touches
3 conflicts
0xd5f3026c…9429
0x968279…9342
6 touches
3 conflicts
0x9f1bb850…546d
0x968279…9342
6 touches
3 conflicts
0x9f1bb850…546f
0x968279…9342
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 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: 0x96827978…f09342
3 conflicts on slot 0xd5f3026c6b…fc9423
Audit this contract →
← previous block·next block →recent activity