← previous blocknext block →recent activity
Analyzing
Block #87,409,513
19 transactions · 17 stateful · 2026-07-13 04:05:48 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,409,513 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w39w310w411w512w618w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
12 touches
15 conflicts
0xa099602a…7731
0x34b655…2a6f
8 touches
6 conflicts
0xb5c1ae56…437a
0x34b655…2a6f
8 touches
6 conflicts
0x00842ba8…bdc6
0x34b655…2a6f
6 touches
3 conflicts
0x1c4970af…8823
0x34b655…2a6f
6 touches
3 conflicts
0x731f1834…ef5f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe45b813c…e7c5
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
15 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity