← previous blocknext block →recent activity
Analyzing
Block #87,708,244
49 transactions · 36 stateful · 2026-07-14 13:24:16 UTC
Parallelism
73/100
Blocked
72%
Avg conflicts / tx
2.63
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,708,244 · 49 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w19w210w311w412w513w614w715w816w917w1018w1119w1233w334w235w436w337w539w141w646w847w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x0363d65e…06d2
0x34b655…2a6f
10 touches
10 conflicts
0x4560e5a8…b741
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x7837c02d…0965
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity