← previous blocknext block →recent activity
Analyzing
Block #87,588,044
38 transactions · 24 stateful · 2026-07-14 00:00:31 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,588,044 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w08w116w017w118w119w220w321w425w526w627w729w630w831w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x745952b2…d90c
0x34b655…2a6f
12 touches
15 conflicts
0xc0e4d476…712c
0x34b655…2a6f
12 touches
15 conflicts
0x8391fb68…4c83
0x34b655…2a6f
10 touches
10 conflicts
0x691e3505…dd2f
0x34b655…2a6f
10 touches
10 conflicts
0x4e86f6b3…99b7
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa7ff2c07…b2ad
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity