← previous blocknext block →recent activity
Analyzing
Block #87,497,582
13 transactions · 13 stateful · 2026-07-13 13:54:42 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,497,582 · 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
4w05w16w07w28w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32dfa6a9…12f6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x973729b4…d3fb
0x34b655…2a6f
6 touches
3 conflicts
0x6f9c6bd9…c66c
0x34b655…2a6f
4 touches
1 conflict
0x6fa48528…fdbd
0x34b655…2a6f
4 touches
1 conflict
0x84b625c0…1e1c
0x34b655…2a6f
4 touches
1 conflict
0x8b7af792…9ef0
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
6 conflicts on slot 0x32dfa6a9da…8f12f6
Audit this contract →
← previous block·next block →recent activity