← previous blocknext block →recent activity
Analyzing
Block #95,270,596
12 transactions · 11 stateful · 2026-08-12 06:09:39 UTC
Parallelism
33/100
Blocked
64%
Avg conflicts / tx
2.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,270,596 · 12 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d47cc34…a3b1
0x40c49f…2af0
16 touches
28 conflicts
0x2b54cadb…4425
0xd18b7e…414b
16 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
16 touches
28 conflicts
0x002fed35…79fa
0x2a68ba…90c5
16 touches
28 conflicts
0xfa70f6bb…ea94
0xd18b7e…414b
4 touches
1 conflict
0xaff5e04d…31f7
0x754704…b603
4 touches
1 conflict
0x0b10a52b…ac19
0xd18b7e…414b
4 touches
1 conflict
0x33b392cc…4b28
0xd18b7e…414b
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: 0x40c49f17…d22af0
28 conflicts on slot 0x8d47cc3483…3da3b1
Audit this contract →
← previous block·next block →recent activity