← previous blocknext block →recent activity
Analyzing
Block #95,716,043
13 transactions · 9 stateful · 2026-08-13 19:36:01 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,716,043 · 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
3w05w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1f9150…430f
0x34b655…2a6f
8 touches
6 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe3321cb6…26de
0x34b655…2a6f
4 touches
1 conflict
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xa2e89145…7dfa
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 0xcd1f91506d…e8430f
Audit this contract →
← previous block·next block →recent activity