← previous blocknext block →recent activity
Analyzing
Block #95,373,911
13 transactions · 13 stateful · 2026-08-12 14:52:34 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,373,911 · 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
2w03w04w15w28w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xd569ba81…2f0c
0x34b655…2a6f
4 touches
1 conflict
0xda3c3c2e…e09a
0x34b655…2a6f
4 touches
1 conflict
0xdb3937e8…23cb
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
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
3 conflicts on slot 0xf0d45ffdb0…4089cf
Audit this contract →
← previous block·next block →recent activity