← previous blocknext block →recent activity
Analyzing
Block #95,075,992
21 transactions · 21 stateful · 2026-08-11 13:42:02 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,075,992 · 21 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
2w04w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25205c26…56c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5a0a2b03…ac50
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
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
3 conflicts on slot 0x25205c2640…8e56c9
Audit this contract →
← previous block·next block →recent activity