← previous blocknext block →recent activity
Analyzing
Block #96,014,834
6 transactions · 5 stateful · 2026-08-14 20:39:17 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,014,834 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d372d00…8884
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x93f2aa04…598c
0x34b655…2a6f
4 touches
1 conflict
0x03b80be8…1214
0x34b655…2a6f
2 touches
0 conflicts
0x07d94be1…7fa8
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: Perpl
1 conflict on slot 0x1d372d0005…218884
Audit this contract →
← previous block·next block →recent activity