← previous blocknext block →recent activity
Analyzing
Block #95,637,564
24 transactions · 22 stateful · 2026-08-13 13:00:15 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,637,564 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w08w19w210w315w216w317w018w119w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
8 touches
6 conflicts
0xa59e109d…d53b
0x851145…3f07
6 touches
3 conflicts
0xc0364fa8…181e
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xf9312173…41a7
0x851145…3f07
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…4737
0x1b6862…e19c
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: 0x59df8637…6d2780
6 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity