← previous blocknext block →recent activity
Analyzing
Block #87,761,539
22 transactions · 17 stateful · 2026-07-14 19:20:56 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,761,539 · 22 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
1w02w14w05w19w210w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe540c5fa…c713
0x0a2fbf…29b1
6 touches
3 conflicts
0xb9a4ecc0…c1ea
0x0a2fbf…29b1
6 touches
3 conflicts
0xb9a4ecc0…c1eb
0x0a2fbf…29b1
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x33da0dfa…bac6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 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
3 conflicts on slot 0xe540c5fa3a…7dc713
Audit this contract →
← previous block·next block →recent activity