← previous blocknext block →recent activity
Analyzing
Block #95,549,287
13 transactions · 12 stateful · 2026-08-13 05:36:15 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,549,287 · 13 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
1w02w13w04w05w16w27w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6266e26a…96ee
0x34b655…2a6f
6 touches
3 conflicts
0x0c78ade3…f11a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0x6ef9b7ed…af56
0x34b655…2a6f
6 touches
3 conflicts
0xe6624a75…5ff4
0x34b655…2a6f
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x6266e26a7e…5096ee
Audit this contract →
← previous block·next block →recent activity