← previous blocknext block →recent activity
Analyzing
Block #87,616,835
20 transactions · 16 stateful · 2026-07-14 03:13:04 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,616,835 · 20 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
1w02w13w04w16w010w011w114w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed4a0d72…065f
0x34b655…2a6f
4 touches
1 conflict
0xa5ab7b8a…c97b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca3f1796…927c
0x34b655…2a6f
4 touches
1 conflict
0xcf827da3…f2a5
0x34b655…2a6f
4 touches
1 conflict
0xde980d9c…7f68
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xed4a0d72e2…41065f
Audit this contract →
← previous block·next block →recent activity