← previous blocknext block →recent activity
Analyzing
Block #87,612,044
59 transactions · 44 stateful · 2026-07-14 02:41:01 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
1.95
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,612,044 · 59 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w211w012w113w215w016w017w218w319w435w636w737w840w941w147w349w454w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
8 touches
6 conflicts
0x8efad608…60bc
0xd32edf…ff58
7 touches
6 conflicts
0x92c17fb5…c032
0x34b655…2a6f
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity