← previous blocknext block →recent activity
Analyzing
Block #87,918,677
45 transactions · 34 stateful · 2026-07-15 12:52:00 UTC
Parallelism
62/100
Blocked
62%
Avg conflicts / tx
1.67
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,918,677 · 45 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w112w013w114w015w118w119w220w321w422w526w327w630w832w137w938w1040w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe63a9ab2…a44f
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
12 touches
15 conflicts
0x6bd6b33e…9557
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity