← previous blocknext block →recent activity
Analyzing
Block #95,425,328
13 transactions · 11 stateful · 2026-08-12 19:12:44 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,425,328 · 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
2w05w06w17w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x3b299648…f5cf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1c8753e8…d214
0x34b655…2a6f
4 touches
1 conflict
0x972e38eb…dc76
0x34b655…2a6f
4 touches
1 conflict
0xdcd1a070…7e92
0x34b655…2a6f
2 touches
0 conflicts
0xe88295cd…5eb9
0x34b655…2a6f
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
1 conflict on slot 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity