← previous blocknext block →recent activity
Analyzing
Block #87,905,526
16 transactions · 14 stateful · 2026-07-15 11:24:03 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,905,526 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w010w112w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f3ece3…c237
0x34b655…2a6f
4 touches
1 conflict
0x461a3556…5948
0x34b655…2a6f
4 touches
1 conflict
0x84585d11…6ae7
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276c
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276d
0x34b655…2a6f
4 touches
1 conflict
0xca529dbd…dc62
0x34b655…2a6f
4 touches
1 conflict
0xd983f81a…73a7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x30f3ece315…53c237
Audit this contract →
← previous block·next block →recent activity