← previous blocknext block →recent activity
Analyzing
Block #95,625,237
23 transactions · 20 stateful · 2026-08-13 11:58:15 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,625,237 · 23 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
2w03w15w26w37w48w512w013w114w215w316w417w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2391abe…d635
0x34b655…2a6f
12 touches
15 conflicts
0x5026f3d8…2508
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d61
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d62
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d65
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d66
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d68
0x968279…9342
10 touches
10 conflicts
0x5026f3d8…2505
0x968279…9342
10 touches
10 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
15 conflicts on slot 0xc2391abed2…7fd635
Audit this contract →
← previous block·next block →recent activity