← previous blocknext block →recent activity
Analyzing
Block #87,513,862
22 transactions · 22 stateful · 2026-07-13 15:43:41 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,513,862 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w08w19w210w313w114w215w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1274880c…3cdc
0x34b655…2a6f
4 touches
1 conflict
0x59037442…7fd5
0x34b655…2a6f
4 touches
1 conflict
0x69a0a437…758c
0x34b655…2a6f
4 touches
1 conflict
0x78cbb28a…27c3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x158622…375e
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity