← previous blocknext block →recent activity
Analyzing
Block #87,496,816
36 transactions · 29 stateful · 2026-07-13 13:49:34 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
1.86
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,496,816 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w29w010w115w116w217w318w419w520w624w225w726w827w928w329w431w1032w1133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
8 touches
6 conflicts
0x6280c6c6…11ac
0x34b655…2a6f
8 touches
6 conflicts
0xaa198c38…7b0a
0x34b655…2a6f
6 touches
3 conflicts
0xb670a63e…ead8
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity