← previous blocknext block →recent activity
Analyzing
Block #85,198,224
45 transactions · 37 stateful · 2026-07-02 22:02:38 UTC
Parallelism
64/100
Blocked
78%
Avg conflicts / tx
2
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #85,198,224 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w110w011w112w213w314w416w017w118w219w320w421w522w623w725w126w228w329w430w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xb44564d6…bb43
0x34b655…2a6f
10 touches
10 conflicts
0xb04d17a0…10e8
0x34b655…2a6f
8 touches
6 conflicts
0x8d24fe06…31f4
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0xc824469a…6425
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity