← previous blocknext block →recent activity
Analyzing
Block #96,132,493
13 transactions · 10 stateful · 2026-08-15 06:31:12 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,132,493 · 13 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
2w06w17w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x3c3621c7…3e11
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x24f6d4ca…c33b
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 0xf726e2e2be…1fe561
Audit this contract →
← previous block·next block →recent activity