← previous blocknext block →recent activity
Analyzing
Block #95,024,379
21 transactions · 20 stateful · 2026-08-11 09:21:37 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,024,379 · 21 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
1w02w13w04w15w26w38w49w510w011w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x13a332bb…0a80
0x34b655…2a6f
4 touches
1 conflict
0x15554b7b…e30e
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x348ae643…36cb
0x34b655…2a6f
4 touches
1 conflict
0x59037442…7fd5
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
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
21 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity