← previous blocknext block →recent activity
Analyzing
Block #96,023,253
10 transactions · 10 stateful · 2026-08-14 21:21:42 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,023,253 · 10 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
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b96981…ef48
0x34b655…2a6f
4 touches
1 conflict
0x2a1544ad…9f70
0x34b655…2a6f
4 touches
1 conflict
0x2e70e07e…48db
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x596ab493…b0e9
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xc2cce19d…4ad4
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 0x27b969810f…26ef48
Audit this contract →
← previous block·next block →recent activity