← previous blocknext block →recent activity
Analyzing
Block #96,357,514
10 transactions · 10 stateful · 2026-08-16 01:22:58 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,357,514 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2776eefc…3c26
0x065c9d…c394
2 touches
0 conflicts
0xb26bd49d…ce24
0x065c9d…c394
2 touches
0 conflicts
0xcb096908…854e
0x065c9d…c394
2 touches
0 conflicts
0x317fc387…8bf2
0x0a3323…0a3c
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 0x52c63247e1…bace02
Audit this contract →
← previous block·next block →recent activity