← previous blocknext block →recent activity
Analyzing
Block #95,201,038
18 transactions · 16 stateful · 2026-08-12 00:11:01 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,201,038 · 18 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
2w03w16w07w18w29w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc5ca07…1020
0xe52b14…7230
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0x12732b88…d3cb
0xe52b14…7230
8 touches
6 conflicts
0x544b41ee…5b5b
0xe52b14…7230
6 touches
6 conflicts
0xd42c0a7f…ecdf
0xe52b14…7230
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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