← previous blocknext block →recent activity
Analyzing
Block #87,610,823
16 transactions · 14 stateful · 2026-07-14 02:32:52 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,610,823 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w17w28w19w210w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa10e928f…3b92
0x34b655…2a6f
6 touches
3 conflicts
0xd732bc76…2844
0x34b655…2a6f
6 touches
3 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
6 touches
3 conflicts
0x3fc24edc…9ff2
0x34b655…2a6f
4 touches
1 conflict
0x89b7c544…35e0
0x34b655…2a6f
4 touches
1 conflict
0x9a1c0572…4c15
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
10 conflicts on slot 0xd93edb3f20…0394ec
Audit this contract →
← previous block·next block →recent activity