← previous blocknext block →recent activity
Analyzing
Block #95,179,456
16 transactions · 15 stateful · 2026-08-11 22:22:29 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,179,456 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c89f9d…f5bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00dcbc22…8053
0x34b655…2a6f
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x2285ffd3…961c
0x34b655…2a6f
2 touches
0 conflicts
0x3270f906…a0e9
0x34b655…2a6f
2 touches
0 conflicts
0x7abe0396…ab27
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 0x00c89f9d54…04f5bf
Audit this contract →
← previous block·next block →recent activity