← previous blocknext block →recent activity
Analyzing
Block #95,244,701
11 transactions · 10 stateful · 2026-08-12 03:51:22 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,244,701 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc5ca07…1020
0xe52b14…7230
8 touches
6 conflicts
0x6ba00dc0…4e53
0xe52b14…7230
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xa36cb1a6…efed
0xe52b14…7230
6 touches
6 conflicts
0x8fc6a560…b612
0xe52b14…7230
6 touches
3 conflicts
0x29f0c836…aff7
0xe52b14…7230
5 touches
3 conflicts
0x261cbea7…e35e
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: 0xe52b1424…bb7230
6 conflicts on slot 0x6cc5ca0712…1f1020
Audit this contract →
← previous block·next block →recent activity