← previous blocknext block →recent activity
Analyzing
Block #95,021,501
12 transactions · 11 stateful · 2026-08-11 09:07:09 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,021,501 · 12 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
1w02w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a921be0…779c
0x2a68ba…90c5
8 touches
6 conflicts
0xfb45f7cb…05c3
0x40c49f…2af0
7 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x3a921be0eb…41779c
Audit this contract →
← previous block·next block →recent activity