← previous blocknext block →recent activity
Analyzing
Block #95,636,645
20 transactions · 18 stateful · 2026-08-13 12:55:38 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,636,645 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w29w310w115w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
10 touches
10 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x9fd4ce93…ae4e
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x4295a3f8…97a1
0x34b655…2a6f
2 touches
0 conflicts
0x588380ee…0a5c
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: 0x59df8637…6d2780
10 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity