← previous blocknext block →recent activity
Analyzing
Block #96,340,266
18 transactions · 16 stateful · 2026-08-15 23:56:13 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,340,266 · 18 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
1w02w13w14w05w18w09w110w212w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xca995928…ded0
0x34b655…2a6f
4 touches
1 conflict
0x78b7945b…2113
0x34b655…2a6f
4 touches
1 conflict
0x7afbac8f…9cad
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity