← previous blocknext block →recent activity
Analyzing
Block #85,123,483
38 transactions · 31 stateful · 2026-07-02 13:44:35 UTC
Parallelism
63/100
Blocked
77%
Avg conflicts / tx
2.26
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #85,123,483 · 38 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w311w012w113w014w115w216w317w418w519w620w724w325w126w427w132w934w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x742072b0…1af8
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x59645a97…3ca1
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x04105a34…6eea
0x34b655…2a6f
8 touches
6 conflicts
0x5d7f309d…5145
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity