← previous blocknext block →recent activity
Analyzing
Block #87,498,285
18 transactions · 14 stateful · 2026-07-13 13:59:24 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,498,285 · 18 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
1w02w13w04w17w28w29w310w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x57b57f51…2449
0x34b655…2a6f
6 touches
3 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
4 touches
1 conflict
0x21aca45f…3e3a
0x34b655…2a6f
4 touches
1 conflict
0x2b9682b4…804e
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a361
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity