← previous blocknext block →recent activity
Analyzing
Block #96,221,213
14 transactions · 11 stateful · 2026-08-15 13:57:25 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,221,213 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5d53a1…ad5f
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x2895e9ff…95e9
0x34b655…2a6f
2 touches
0 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
2 touches
0 conflicts
0x42c4bc0a…ecb6
0x34b655…2a6f
2 touches
0 conflicts
0xa359130f…4254
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
1 conflict on slot 0xeb5d53a114…6fad5f
Audit this contract →
← previous block·next block →recent activity