← previous blocknext block →recent activity
Analyzing
Block #95,297,324
10 transactions · 9 stateful · 2026-08-12 08:24:33 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,297,324 · 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
1w02w13w25w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x446f2734…8b54
0x0a3323…0a3c
6 touches
3 conflicts
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f4
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x3978cfea…d66e
0x34b655…2a6f
2 touches
0 conflicts
0x3a5cd535…3546
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: 0x0a332311…6e0a3c
3 conflicts on slot 0x446f273453…878b54
Audit this contract →
← previous block·next block →recent activity