← previous blocknext block →recent activity
Analyzing
Block #87,621,813
21 transactions · 17 stateful · 2026-07-14 03:46:19 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,621,813 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w410w011w513w014w115w217w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x640530ff…86bc
0x34b655…2a6f
6 touches
3 conflicts
0x9effa23c…8601
0x34b655…2a6f
6 touches
3 conflicts
0xc6dacce8…0666
0x34b655…2a6f
6 touches
3 conflicts
0x09a15b10…2639
0x754704…b603
6 touches
3 conflicts
0x5149ba0e…d954
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: Perpl
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity