← previous blocknext block →recent activity
Analyzing
Block #87,579,044
19 transactions · 17 stateful · 2026-07-13 23:00:20 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,579,044 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w37w08w19w213w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07f69062…03ec
0x34b655…2a6f
10 touches
10 conflicts
0x925c118c…a1d8
0x34b655…2a6f
8 touches
6 conflicts
0xa4c5bece…7f7c
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7a0f6376…1034
0x34b655…2a6f
6 touches
3 conflicts
0x8b789f68…8ace
0x34b655…2a6f
6 touches
3 conflicts
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x07f6906240…ea03ec
Audit this contract →
← previous block·next block →recent activity