← previous blocknext block →recent activity
Analyzing
Block #95,087,507
16 transactions · 14 stateful · 2026-08-11 14:39:58 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,087,507 · 16 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
1w02w03w14w09w010w111w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0a395cd…12ce
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xfcfb570f…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xf0a395cda0…5c12ce
Audit this contract →
← previous block·next block →recent activity