← previous blocknext block →recent activity
Analyzing
Block #85,188,403
64 transactions · 42 stateful · 2026-07-02 20:57:13 UTC
Parallelism
77/100
Blocked
60%
Avg conflicts / tx
1.84
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,188,403 · 64 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
2w03w04w08w010w117w018w019w120w021w122w223w324w425w526w129w130w234w340w341w650w1152w1255w1458w259w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xfc366eef…6209
0x34b655…2a6f
11 touches
15 conflicts
0xb44564d6…bb43
0x34b655…2a6f
10 touches
10 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x22e0cc1d…ad0d
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity