← previous blocknext block →recent activity
Analyzing
Block #87,341,092
17 transactions · 17 stateful · 2026-07-12 20:28:12 UTC
Parallelism
35/100
Blocked
65%
Avg conflicts / tx
2.24
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,341,092 · 17 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w37w49w510w614w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xbc94dfe1…0b3d
0x34b655…2a6f
10 touches
10 conflicts
0xe3ce81c6…d48d
0x34b655…2a6f
8 touches
6 conflicts
0xe85e763f…3b25
0x34b655…2a6f
8 touches
6 conflicts
0x86d1a3fb…ed61
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity