← previous blocknext block →recent activity
Analyzing
Block #95,635,938
30 transactions · 27 stateful · 2026-08-13 12:52:05 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,635,938 · 30 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
2w03w14w05w16w27w18w210w011w112w213w014w119w221w322w126w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xa4dae615…1cf8
0x34b655…2a6f
4 touches
1 conflict
0xa7a84000…dd34
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity