← previous blocknext block →recent activity
Analyzing
Block #95,078,067
16 transactions · 13 stateful · 2026-08-11 13:52:28 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,078,067 · 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
1w02w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0x2b652efc…049b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x042a182d…e7f9
0x065c9d…c394
2 touches
0 conflicts
0x2d4a35a4…e128
0x065c9d…c394
2 touches
0 conflicts
0x484b0d1c…9ccd
0x065c9d…c394
2 touches
0 conflicts
0xbf8c2bc5…d5a0
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xcda18b0bef…046a4c
Audit this contract →
← previous block·next block →recent activity