← previous blocknext block →recent activity
Analyzing
Block #87,761,513
21 transactions · 16 stateful · 2026-07-14 19:20:45 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,761,513 · 21 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
1w02w13w06w07w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0xb9a4ecc0…c1ea
0x0a2fbf…29b1
8 touches
6 conflicts
0xb9a4ecc0…c1eb
0x0a2fbf…29b1
8 touches
6 conflicts
0xe540c5fa…c70f
0x0a2fbf…29b1
8 touches
6 conflicts
0xe540c5fa…c710
0x0a2fbf…29b1
8 touches
6 conflicts
0xe540c5fa…c713
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity