← previous blocknext block →recent activity
Analyzing
Block #87,295,640
18 transactions · 17 stateful · 2026-07-12 15:24:17 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,295,640 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w311w413w515w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x974c36fe…1cd7
0x34b655…2a6f
8 touches
6 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xd2b44b36…b48d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x57f6fade…9347
0x34b655…2a6f
4 touches
1 conflict
0x5d471730…eadc
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity