← previous blocknext block →recent activity
Analyzing
Block #87,408,711
15 transactions · 15 stateful · 2026-07-13 04:00:26 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,408,711 · 15 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
1w02w13w16w28w310w313w014w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13b266ee…b6a0
0x34b655…2a6f
4 touches
1 conflict
0x2244bba9…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
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 0x13b266eebf…abb6a0
Audit this contract →
← previous block·next block →recent activity