← previous blocknext block →recent activity
Analyzing
Block #96,135,664
13 transactions · 12 stateful · 2026-08-15 06:47:10 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,135,664 · 13 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
2w03w14w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x818e1296…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xa366fc53…ed2a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x60d67be4…56ab
0x065c9d…c394
2 touches
0 conflicts
0x8977de71…d87e
0x065c9d…c394
2 touches
0 conflicts
0x9e1a89c0…fe4e
0x065c9d…c394
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 0x818e12964c…2af4d7
Audit this contract →
← previous block·next block →recent activity