← previous blocknext block →recent activity
Analyzing
Block #87,355,425
39 transactions · 36 stateful · 2026-07-12 22:04:00 UTC
Parallelism
62/100
Blocked
72%
Avg conflicts / tx
3.1
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,355,425 · 39 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w39w410w511w612w713w815w316w420w222w523w324w426w133w1036w1238w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x20b3ddc1…6079
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x2aad2854…698e
0x34b655…2a6f
12 touches
15 conflicts
0x2ae5c11f…95f3
0x34b655…2a6f
12 touches
15 conflicts
0x321eac33…6aca
0x34b655…2a6f
12 touches
15 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity