← previous blocknext block →recent activity
Analyzing
Block #96,286,921
8 transactions · 6 stateful · 2026-08-15 19:27:55 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,286,921 · 8 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
2w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca86fe92…6b3b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x356f7cea…cbd1
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
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 0xca86fe92d5…3c6b3b
Audit this contract →
← previous block·next block →recent activity