← previous blocknext block →recent activity
Analyzing
Block #96,664,043
15 transactions · 12 stateful · 2026-08-17 03:04:58 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,664,043 · 15 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
3w04w05w17w08w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
2 touches
0 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: Perpl
3 conflicts on slot 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity