← previous blocknext block →recent activity
Analyzing
Block #87,356,159
25 transactions · 23 stateful · 2026-07-12 22:08:55 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,356,159 · 25 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
1w02w14w29w012w013w115w016w217w118w319w321w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x86fc6de5…176a
0x065c9d…c394
5 touches
3 conflicts
0x1a18db64…1d9c
0x065c9d…c394
5 touches
3 conflicts
0x4e4a90db…ea1f
0x065c9d…c394
5 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity