← previous blocknext block →recent activity
Analyzing
Block #87,682,688
25 transactions · 22 stateful · 2026-07-14 10:33:09 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,682,688 · 25 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
1w04w16w07w08w19w110w211w315w017w118w219w020w221w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x647a9286…61c1
0x34b655…2a6f
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity