← previous blocknext block →recent activity
Analyzing
Block #95,151,484
20 transactions · 19 stateful · 2026-08-11 20:01:47 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,151,484 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w28w310w411w512w113w014w616w218w219w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x2df04977…8fa9
0x34b655…2a6f
4 touches
1 conflict
0xde7bb688…2b68
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
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
10 conflicts on slot 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity