← previous blocknext block →recent activity
Analyzing
Block #96,023,594
19 transactions · 17 stateful · 2026-08-14 21:23:25 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,023,594 · 19 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
2w03w14w06w19w010w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x124a2fe8…2ea9
0x34b655…2a6f
4 touches
1 conflict
0x72ed31c7…de4d
0x34b655…2a6f
4 touches
1 conflict
0x8435cea0…f5b6
0x34b655…2a6f
4 touches
1 conflict
0xb8b82811…8b9e
0x34b655…2a6f
4 touches
1 conflict
0x15864863…568b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
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: Perpl
1 conflict on slot 0x124a2fe822…4a2ea9
Audit this contract →
← previous block·next block →recent activity