← previous blocknext block →recent activity
Analyzing
Block #87,595,162
17 transactions · 13 stateful · 2026-07-14 00:48:08 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,595,162 · 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
1w02w16w08w112w213w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7af8195…cea4
0x34b655…2a6f
4 touches
1 conflict
0xd7fe05cd…207e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdcd47ab6…d8f9
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0804b2ba…8a77
0x34b655…2a6f
4 touches
1 conflict
0x10fec71b…e12f
0x34b655…2a6f
4 touches
1 conflict
0x2e30c36b…b1fa
0x34b655…2a6f
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
1 conflict on slot 0xf7af81950d…8ccea4
Audit this contract →
← previous block·next block →recent activity