← previous blocknext block →recent activity
Analyzing
Block #87,489,889
17 transactions · 17 stateful · 2026-07-13 13:03:14 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,489,889 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w37w410w311w412w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdbc62196…3245
0x34b655…2a6f
6 touches
3 conflicts
0xe2c66a2e…150f
0x34b655…2a6f
6 touches
3 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
6 touches
3 conflicts
0x4e6132eb…d2fe
0x34b655…2a6f
6 touches
3 conflicts
0x24c5ef3e…128c
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
6 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity