← previous blocknext block →recent activity
Analyzing
Block #95,641,806
32 transactions · 30 stateful · 2026-08-13 13:21:36 UTC
Parallelism
38/100
Blocked
67%
Avg conflicts / tx
5.97
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #95,641,806 · 32 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1618w1719w1820w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
40 touches
190 conflicts
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0x7d81ec7b…64c3
0x34b655…2a6f
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x36ea7103…72ef
0x447d2e…e9f5
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: 0x59df8637…6d2780
190 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity