← previous blocknext block →recent activity
Analyzing
Block #96,268,142
10 transactions · 10 stateful · 2026-08-15 17:53:28 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,268,142 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0xaf90b3f4…5873
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x408e66bba7…d43d6b
Audit this contract →
← previous block·next block →recent activity