← previous blocknext block →recent activity
Analyzing
Block #87,792,117
30 transactions · 27 stateful · 2026-07-14 22:45:31 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,792,117 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w615w123w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x26050074…6967
0x34b655…2a6f
12 touches
15 conflicts
0x28c62bca…b746
0x34b655…2a6f
12 touches
15 conflicts
0x8d989c17…e984
0x34b655…2a6f
12 touches
15 conflicts
0x9ae859db…2d84
0x34b655…2a6f
12 touches
15 conflicts
0xa633ba40…7766
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity