← previous blocknext block →recent activity
Analyzing
Block #87,612,981
47 transactions · 41 stateful · 2026-07-14 02:47:17 UTC
Parallelism
57/100
Blocked
76%
Avg conflicts / tx
3.23
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,612,981 · 47 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w49w011w012w113w214w315w417w118w219w332w1534w337w538w642w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…0001
0xc1ff9f…b0fc
12 touches
15 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
8 touches
6 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity