← previous blocknext block →recent activity
Analyzing
Block #96,115,333
10 transactions · 9 stateful · 2026-08-15 05:04:50 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,115,333 · 10 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
1w02w13w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0cd9fc1…1c44
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd106eb58…b2b1
0x34b655…2a6f
4 touches
1 conflict
0xe6997d36…4f33
0x34b655…2a6f
4 touches
1 conflict
0xfd9bfada…b65b
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
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 0xc0cd9fc147…b21c44
Audit this contract →
← previous block·next block →recent activity