← previous blocknext block →recent activity
Analyzing
Block #87,621,338
13 transactions · 12 stateful · 2026-07-14 03:43:09 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,621,338 · 13 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
2w03w16w07w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09fdd670…f43c
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x0c7dc850…4019
0x34b655…2a6f
4 touches
1 conflict
0x1ba8b92c…68c1
0x34b655…2a6f
4 touches
1 conflict
0x26eb910e…e23a
0x34b655…2a6f
4 touches
1 conflict
0x26ec5722…ae71
0x34b655…2a6f
4 touches
1 conflict
0x2c438b07…8b3d
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
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 0x09fdd67091…1ef43c
Audit this contract →
← previous block·next block →recent activity