← previous blocknext block →recent activity
Analyzing
Block #87,710,391
27 transactions · 26 stateful · 2026-07-14 13:38:39 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,710,391 · 27 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
2w03w14w25w07w08w19w210w314w115w016w118w219w320w222w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
8 touches
6 conflicts
0x3a4ed784…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0xbf768a2f…f453
0x34b655…2a6f
8 touches
6 conflicts
0xdfbd8991…5bd1
0x34b655…2a6f
8 touches
6 conflicts
0x015c28a0…37da
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x6fe7d366…78ff
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
6 conflicts on slot 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity